Microsoft Solutions Partner Designation Certification

Measuring your capabilities as a partner organization your Microsoft Solutions Partner designation certification in 2025 and beyond spans six key solution areas: Business Applications, Modern Work, Security, Data & AI (Azure), Digital & App Innovation (Azure), and Infrastructure (Azure).

Attaining any of these designations requires a Partner Capability Score of at least 70 out of 100 for that solution area. The score is earned across three categories – performance, skilling, and customer success – ensuring a holistic evaluation of a partner’s real-world impact, not just technical knowledge. Importantly, partners must score at least 1 point in each subcategory (i.e. you can’t skip any area entirely) while reaching the 70-point threshold. Below is a breakdown of the requirements and scoring criteria for each solution area, highlighting how points are earned:

Business Applications

Focus: Dynamics 365 (CRM/ERP) and Power Platform solutions. This designation reflects broad capability in delivering business application solutions (e.g. ERP, CRM, low-code apps) to customers.

• Performance (Net Customer Additions): Measures how many new customer deployments of Dynamics 365 or Power Platform workloads you’ve driven in the past 12 months. For the Enterprise path, a “net new customer” generally means adding a customer with significant Dynamics 365/Power Platform subscription value (e.g. >$1,500 USD in active subscription). In the SMB path, the threshold is lower (e.g. new customers with >$250 USD subscription count as adds). Each new customer contributes points up to a maximum (e.g. 5 enterprise adds or 10 SMB adds may yield the full 20 points in this category). Both Enterprise and SMB tracks are evaluated automatically, and the higher score counts.
• Customer Success: Emphasizes usage growth and deployments of business applications. Partners earn points by expanding usage of Dynamics 365/Power Platform in existing customers (measured via workload usage growth or larger solution deployments year-over-year). For example, increasing the number of active Dynamics 365 seats or usage of Power Platform services across tenants will contribute to usage growth Additionally, completing successful deployments of specific workloads (such as implementing a new Dynamics 365 module or Power Platform solution for a customer) yields points. These metrics ensure partners not only win new customers but also drive deeper adoption in their customer base.
• Skilling: Requires a team of certified experts in Business Applications. Points are split between Intermediate (Associate-level) and Advanced (Expert-level) certifications. Qualifying certifications include Dynamics 365 Functional Consultant Associate credentials (e.g. in Finance, Sales, Customer Service, Business Central) and Power Platform certifications for the intermediate tier, and Solution Architect Expert certifications for the advanced tier. To get full points, a certain number of team members must hold these certifications (e.g. for an enterprise, typically ~4 individuals with associate certs and 2 with expert certs; fewer are required on the SMB path) – but at minimum, at least one associate and one expert cert holder are needed to score any points in each sub-metric. This skilling requirement ensures the partner has personnel proficient in Dynamics 365/Power Platform deployment and architecture.

Modern Work

Focus: Microsoft 365 and productivity solutions. This designation demonstrates capability in deploying and managing Microsoft 365 services (Office 365, Teams, etc.) and enabling hybrid work.

• Performance (Net Customer Additions): Measures net new Microsoft 365 customer tenants added in the last year. In the Enterprise path, a new customer counts if they deploy >300 paid Microsoft 365 seats (licenses) in a workload. In the SMB path, a new customer is one with between 11 and 300 seats (mid-market size). The scoring model differs by path: for Enterprise, each new customer might be worth ~4 points (maxing out after 5 customers for 20 points), whereas for SMB each new customer is ~2 points (maxing after 10 customers). The idea is to give equal opportunity – smaller deals count on the SMB track, while enterprise deals carry more weight.
• Customer Success: Consists of two metrics – Usage Growth and Deployments. Usage Growth tracks how much you’ve increased active use of Microsoft 365 services in your customer base (e.g. growth in Teams active users, Exchange mailbox usage, SharePoint storage consumed, etc., compared to the previous year). Hitting certain percentage growth benchmarks yields points – this demonstrates you are driving deeper adoption of M365 tools over time. Deployments measures the breadth of Microsoft 365 services deployed to customers. For instance, successfully deploying new workloads like Teams Phone, SharePoint, or Intune for customers counts towards this metric. You earn points by having a certain number of customers actively using multiple workloads, reflecting your ability to implement solutions that expand Microsoft 365’s footprint in organizations. Both usage growth and deployments metrics combined can contribute a significant portion of the 100 points (they typically carry more weight than performance in this solution area).
• Skilling: Focuses on Microsoft 365 technical credentials. Partners need team members certified in Microsoft 365 roles, such as Teams Administrator Associate, Endpoint Administrator, Identity and Access Administrator (Associate level), and at least one Microsoft 365 Certified: Enterprise Administrator Expert. To fulfill the requirements, you must have at least one person with an intermediate M365 certification and one with the advanced (Expert) cert, and more to maximize points. For example, on the Enterprise path, full points might require 4 M365 Associates + 2 Experts, while the SMB path might need 2 Associates + 1 Expert. This ensures partners have proven proficiency in managing and securing Microsoft 365 environments.

Security

Focus: Microsoft Security solutions across Azure and Microsoft 365. This designation validates a partner’s ability to deploy and manage security solutions such as Azure Sentinel, Defender, Entra ID (Azure AD), Microsoft 365 security workloads, etc..

• Performance (Net Customer Additions): Measures new customer organizations you have secured with Microsoft security solutions in the past year. Uniquely, the Security designation considers both Azure security deployments and Microsoft 365 security deployments, reflecting the two domains of security services. An eligible new customer for the Enterprise path might be one that, for example, consumes over $600 USD in Azure security services (ACR) or has >300 seats of M365 security licenses (e.g. EMS or Defender). For the SMB path, a new customer could be one with similar Azure security consumption (≥$600 ACR, as the threshold is the same here) but with a smaller M365 footprint (5–300 seats of M365 security workloads). Points are scored up to a maximum (e.g. 10 new security customers for 20 points, with each track weighted differently: the Enterprise path in Security awards 2 points per customer, whereas SMB awards 4 points per customer — essentially inverted from Modern Work, because Azure security revenue is often a key metric). This performance metric showcases a partner’s success in onboarding new organizations to Microsoft’s security platforms.
• Customer Success: Similar to other areas, Security tracks Usage Growth and Deployments. Here, usage growth might mean increases in Azure security consumption (growth in Azure Sentinel logs, Defender for Cloud usage, etc.) or growth in usage of Microsoft 365 security features (more devices onboarded to Defender, more identities protected by Entra ID P1/P2, etc.) year-over-year. Deployments would measure the number of customers where you have implemented key security solutions (e.g. deploying Sentinel SIEM for a client, or rolling out Microsoft 365 Defender suite to a new customer). Because Security spans cloud and enterprise mobility, Microsoft calculates Azure-related metrics and Microsoft 365-related metrics separately and then combines them. To get points, a partner should demonstrate they have actively increased a customer’s security posture through deploying Microsoft solutions and that those solutions are being actively utilized (the partner capability score will aggregate these successes across all your customers).
• Skilling: Requires certified security professionals on staff. Microsoft typically expects competencies like Microsoft Certified: Security Operations Analyst, Azure Security Engineer Associate, Identity and Access Administrator, Information Protection Administrator, etc., as well as at least one expert-level certification like the Cybersecurity Architect (SC-100). In practice, you might need a couple of associates (SC-200, AZ-500, MS-500 series exams) and at least one expert to satisfy the skilling points. As with other areas, at least one person with an intermediate security cert must be present to score, and similarly an advanced cert holder to fulfill all subcategories. This mix of Azure security and M365 security certifications ensures the partner’s team can design and implement end-to-end security solutions.

Data & AI (Azure)

Focus: Azure data platforms, analytics, and AI services. This designation covers expertise in databases, data warehousing, analytics (e.g. Azure Synapse, Power BI), and AI/machine learning solutions on Azure.

• Performance: Measured by Azure customer growth and consumption. Key metrics include Net Customer Adds (new Azure customers with significant data/AI workloads or Azure consumed revenue), Deployments (number of distinct Azure data/AI services deployed across your customer base), and Usage Growth (year-over-year growth in Azure Consumed Revenue for your customers). For Azure solution areas (Data & AI, Digital App Innovation, Infrastructure), Microsoft defines these metrics similarly. A “net new customer” is typically a customer tenant that started consuming at least a given amount of Azure services (historically ~$1,000/month in Azure consumption, now adjusted for SMB path) in the last year. Deployments count how many distinct Azure services you have running for customers (beyond simple VMs – e.g. deploying Azure SQL, Azure Machine Learning, or Power BI Embedded would count as unique workloads). Usage growth looks at the percentage increase in Azure consumption (ACR) across all your Azure customers compared to the previous year. Scoring in Data & AI performance rewards partners who are growing their Azure data/AI business in both breadth (more services, more customers) and depth (higher usage).
• Customer Success: In Azure-focused designations, customer success overlaps with the performance metrics (since usage growth and deployments are often categorized under customer success). Essentially, Microsoft wants to see that your customers are actively using Azure data and AI services and expanding their usage over time. For example, if you helped a customer migrate a database to Azure or adopt Power BI, Microsoft tracks whether that resource remains in use or grows in consumption. To score high, partners might show significant Azure consumption growth in data/AI services (e.g. increasing TBs of data in Azure SQL or number of Azure AI models deployed) and multiple deployments of different Azure services in production for clients. These factors indicate real customer success stories driven by the partner.
• Skilling: Emphasizes Azure data and AI expertise within the partner’s team. Intermediate certifications for this area include roles like Azure Database Administrator Associate, Azure Data Engineer Associate, Azure AI Engineer Associate, Azure Data Scientist Associate, Power BI Data Analyst Associate, and newer certs such as Azure Cosmos DB Developer Specialty or Fabric Analytics Engineer Associate. For advanced certifications, the Azure Solutions Architect Expert (AZ-305) often counts across Azure solution areas, and there may be specialty expert certs (like Azure Enterprise Data Analyst or related expert-level credentials). To maximize skilling points, you typically need several team members with the associate-level data/AI certs and a couple with an expert cert. Smaller partners (SMB path) can achieve full points with fewer certified individuals (perhaps 2 associates + 1 expert), whereas enterprise path might require more (e.g. 4 associates + 2 experts). This ensures the partner has validated skills in both data management and AI disciplines on Azure.

Digital & App Innovation (Azure)

Focus: Application development and modernization on Azure. This designation (sometimes called “Azure Apps & Innovate”) covers building cloud-native apps, DevOps, application integration, and app modernization capabilities.

• Performance: Uses the same Azure metrics of Net Customer Adds, Deployments, and Usage Growth described above for Azure solution areas. In this context, new customers and growth should specifically relate to Azure application development and PaaS services – for example, acquiring a new customer who starts using Azure App Services or Azure Kubernetes Service via your guidance would count as a net add. Deployments might count the number of unique app services or solutions you’ve deployed (such as containers, web apps, functions, DevOps pipelines set up for clients). Usage growth tracks increases in Azure consumption tied to app innovation workloads (perhaps measured in Azure consumption on services like App Service, Azure Spring Apps, API Management, etc.). The thresholds and scoring logic mirror the other Azure designations.
• Customer Success: Again reflected through deployments of Azure app services and consumption growth. A partner strong in Digital & App Innovation will show evidence of successfully launching new apps on Azure for customers or modernizing existing ones (e.g. moving an on-prem app to Azure PaaS) and those apps sustaining or increasing their usage. Microsoft gauges how many Azure services (excluding basic IaaS VMs) you have running for clients (this showcases breadth of Azure platform adoption). Achieving substantial YOY growth in Azure usage for app innovation projects (for instance, a customer’s Azure spend growing as they shift more application workloads to the cloud) contributes to the score.
• Skilling: Requires Azure application development credentials within the team. Intermediate certs include Azure Developer Associate (AZ-204) and potentially Power Platform Developer Associate (if low-code apps are in scope). Advanced certs focus on architecture and DevOps, such as Azure Solutions Architect Expert (prerequisite for advanced points) and Azure DevOps Engineer Expert, or specialty certs like Azure IoT Developer for relevant scenarios. Typically, two individuals must hold certain prerequisite certs (like Azure Admin Associate and Azure Architect Expert) to unlock scoring, then additional certified individuals contribute points. For full points, an SMB-oriented partner might need a couple of developers and one expert architect certified, whereas an enterprise partner would need a larger cadre of certified developers and architects to reach the maximum 25 points in skilling. This ensures partners have talent proficient in modern cloud app development and DevOps practices.

Infrastructure (Azure)

Focus: Core Azure infrastructure solutions such as VMs, networking, hybrid cloud, and migration of servers/datacenters to Azure. This designation highlights capabilities in Azure compute, networking, storage, and hybrid management.

• Performance: Follows the standard Azure metrics for growth. New customer adds are typically measured by customers whose Azure consumption crosses a threshold (again around $1,000/month traditionally on the enterprise path; with the SMB path now as low as $500/month in Azure spend to count). A “net new” Azure infrastructure customer could be one who started using Azure for the first time with at least that minimal consumption. Deployments looks at distinct Azure infrastructure services deployed (for instance, setting up Azure Virtual Desktop, Azure Arc, or migrating X number of servers to Azure counts toward deployment metrics). Virtual Machines are counted as a baseline service, but Microsoft often excludes counting pure VM provisioning multiple times – instead they reward deploying broader services beyond VMs (like Azure Backup, Azure Monitor, etc.). Usage growth is the percentage growth in Azure consumed revenue for your Azure customers, indicating you are either moving more workloads or expanding usage for existing workloads over the year.
• Customer Success: Demonstrated by successful Azure migrations and expansions. Scoring rewards partners who not only land new Azure infra customers but also grow the cloud footprint for existing customers – e.g., migrating additional servers, increasing Azure VM uptime/usage, or adopting new Azure services for better infrastructure management. A high year-over-year growth in aggregate Azure usage, especially if you had a certain baseline the prior year, is a strong indicator (for instance, partners get full points in usage growth if they grew Azure infrastructure consumption by a set percentage over a baseline of last year’s $X consumption). Additionally, showing multiple Azure services deployed per customer (not just running a few VMs, but using things like Azure Networking, identity, backup, etc.) improves the deployment metric. Essentially, breadth and depth of Azure infrastructure projects deliver the customer success points.
• Skilling: Centers on Azure infrastructure administration and architecture credentials. Typically required are Azure Administrator Associate (AZ-104) as a foundational cert (often a prerequisite), and other associates like Azure Network Engineer, Windows Server Hybrid Administrator, or Azure Stack Hub Operator for intermediate skills. On the advanced side, the Azure Solutions Architect Expert is key (often two architects needed for enterprise path). The partner must have a minimum number of individuals certified (e.g. two admins and one architect for SMB; four admins and two architects for enterprise full points) to demonstrate a solid technical team. Meeting the skilling criteria confirms the partner’s ability to design and manage complex Azure infrastructure setups.

Scoring note: In all solution areas, the Partner Capability Score is calculated automatically from data in Partner Center, using the above metrics. Partners can track their score in real-time and even use a score simulator tool to see how reaching certain targets (like adding a new certified person or gaining another customer) would affect their score. While each area’s metrics are tailored to that domain, Microsoft’s scoring framework is designed such that 70 points is achievable via multiple pathways – for example, a partner could compensate a slightly lower performance score with higher customer success and skilling points, or vice versa. The system is flexible, but it requires a balanced approach: you cannot max out one category and ignore the others, since some points in every category are mandatory.

Benefits and Incentives for Solutions Partners

Achieving a Solutions Partner designation unlocks a rich array of benefits and incentives from Microsoft. These benefits are both core (available across all designations) and incremental (specific to certain solution areas), designed to help partners grow their business, develop their teams, and better serve customers. Below is an overview of key benefits and incentives for partners who attain a Solutions Partner designation:

• Product Use Benefits (Internal Use Rights): Designated partners receive licenses to Microsoft software and cloud services for internal use. This includes Microsoft 365 (Office 365) subscriptions, Windows OS licenses, and significant Azure credit allotments. These internal-use benefits allow your team to run development/test environments, demos, or even your company’s day-to-day IT on the latest Microsoft technologies at no extra cost. (Notably, as of FY2025, Microsoft has expanded these benefits to include newer products like Microsoft Entra ID (Azure AD Premium), Microsoft Defender for Endpoint, and even seats for emerging offerings like Microsoft 365 Copilot, enhancing the value for partners).
• Technical Support and Enablement: Solutions Partners gain elevated support from Microsoft. You receive a set number of partner support incidents for technical issues (for example, to troubleshoot complex Azure problems or get assistance on critical support cases). Additionally, partners get advisory hours or consultative support – this can be used for pre-sales technical guidance, design reviews, or deployment assistance from Microsoft engineers. Access to exclusive technical webinars, advanced training, and readiness materials is also provided to keep your team’s skills sharp. Partners can even purchase discounted advanced support plans if needed, but many find the included support sufficient for most scenarios.
• Go-to-Market (GTM) and Co-Selling Support: Microsoft helps Solutions Partners market and sell their services. Upon attaining a designation, your company is listed with a special badge in Microsoft’s partner directory (the public “Find a Partner” portal), making it easier for customers and Microsoft field teams to find you. Partners also become eligible for co-sell opportunities, meaning Microsoft’s own sellers and account managers may bring you into customer deals or refer customers to you when your expertise is needed. Microsoft provides ready-to-use marketing materials, case study publications, and even funded campaigns for partners with designations. For instance, there are partner marketing kits and “campaign-in-a-box” content tailored to solution areas that you can leverage. Participation in the commercial marketplace (Azure Marketplace or AppSource) is another avenue; partners with solutions or services listed can get greater visibility and priority in the marketplace when they have the Solutions Partner status.
• Financial Incentives and Rebates: Microsoft offers incentive programs that reward partners for driving cloud consumption and customer success. Solutions Partner status often serves as a qualifier or unlock for these incentives. For example, partners transacting via the Cloud Solution Provider (CSP) model can earn rebates or revenue shares on the Azure consumption or Microsoft 365 licenses they drive. Achieving a Solutions Partner designation can increase these incentive rates or make you eligible for additional programs. Microsoft also provides funds for specific activities (like Azure migration assessments, workshops, or proofs-of-concept) under initiatives such as Azure Migrate & Modernize and Azure Innovate – being a designated partner is often required to access these funds. Starting in Microsoft’s FY2026, certain incentive payouts will only be available to Solutions Partners or specialists, phasing out legacy competency-based incentives. In short, the designation can directly boost your profitability through these bonus earnings.
• Recognition and Customer Trust: Attaining a Solutions Partner designation gives you a customer-facing badge and status that signals Microsoft has vetted your skills and experience. This badge can be displayed on your website, marketing materials, and Microsoft partner profile, and it helps you stand out as a top-tier partner. Customers often look for Microsoft designations and certifications when selecting a provider – in fact, Microsoft notes that a majority of customers consider partner credentials and badges as part of their decision process. The designation thus instills confidence that you have proven capabilities. Additionally, within Microsoft’s partner ecosystem, Solutions Partners get invited to exclusive events, technical previews, and communities. You may gain access to programs like the Microsoft Partner Executive Engagements or get priority for awards (e.g. being a Solutions Partner is typically a prerequisite to be considered for Microsoft Partner of the Year in various categories). The prestige associated with the designation is comparable to the old Gold competency, and it demonstrates your organization’s commitment to excellence in that solution area.
• Advanced Specializations Eligibility: Once you earn a Solutions Partner designation, you unlock the ability to pursue specializations (formerly “Advanced Specializations”) and expert programs. These are deeper differentiators – for example, a partner with Solutions Partner for Data & AI might go on to achieve a specialization in Analytics on Azure or AI and Machine Learning on Azure. Specializations involve meeting additional stringent criteria (such as having a certain number of customer projects, reference case studies, and sometimes passing a third-party audit). They come with their own incremental benefits like a special badge, higher priority in Microsoft referral engines, and sometimes additional product benefits or funding beyond what the base designation offers. Moreover, certain elite designations (like Azure Expert Managed Services Provider) require multiple Solutions Partner designations plus specializations. Thus, attaining the Solutions Partner level is a gateway to even greater benefits for those who invest in demonstrating deep expertise.

In summary, the Solutions Partner designation is not just a certificate on the wall – it comes with practical advantages: software and cloud credits to run your business, direct support and training from Microsoft, stronger marketing exposure and sales assistance, monetary incentives, and an enhanced reputation in the market. These benefits are updated periodically to remain valuable – for instance, Microsoft added over 20 new product licenses (like security and AI products) to partner benefits in 2025 to ensure partners have access to the latest technology for internal use. By leveraging these incentives, a Solutions Partner can accelerate growth and deliver even better outcomes for customers, creating a virtuous cycle of success.

Solutions Partner Designation vs. Individual Certifications

It’s important to distinguish a Solutions Partner designation from individual Microsoft certifications, as they serve different purposes and scopes within Microsoft’s ecosystem. While both are forms of validation, one applies to an entire organization and the other to an individual professional:

• Organizational Credential vs. Personal Credential: A Solutions Partner designation is an organization-level achievement – it reflects the collective capabilities and track record of a company. In contrast, an individual Microsoft certification (such as Microsoft Certified: Azure Administrator Associate or Microsoft 365 Certified: Enterprise Administrator Expert) is a personal achievement earned by a single person passing exams. The Solutions Partner badge signifies that the company as a whole has broad technical skills, customer success, and performance in a solution area. Individual certs signify that a specific person has demonstrated knowledge in a particular technology or role.
• Breadth and Proven Experience vs. Depth of Knowledge: The criteria for Solutions Partner are holistic: Microsoft evaluates what the partner has done for customers (performance and success), in addition to having skilled people (certifications). It’s not just theoretical knowledge; it’s a proof of execution at scale. By attaining a Solutions Partner designation, an organization proves it has real-world experience delivering solutions in that area, with multiple projects, multiple certified staff, and documented customer impact. On the other hand, an individual certification focuses on depth of knowledge in a specific domain (like administering Azure, or developing in Power Platform) but does not by itself prove that the holder has delivered successful projects – it’s about competency of one person, typically validated by exams and sometimes a lab.
• Recognition and Use: A Solutions Partner designation is used in marketing and partner differentiation – it’s a badge companies use to promote themselves to clients and it’s listed in Microsoft’s partner directories for customers to find the right partner. It effectively replaced the old Gold/Silver partner labels as the mark of a top-tier Microsoft partner. In contrast, individual certifications are used on personal résumés or profiles (like a consultant’s LinkedIn) and are often prerequisites for partner skilling points (Microsoft counts certified individuals toward the partner’s score). Clients may value that the delivery team has certified experts, but ultimately the Solutions Partner badge gives clients confidence in the organization as a whole, whereas individual certs give confidence in the skills of specific team members.
• Structure and Renewal: To earn a Solutions Partner designation, a company must continually meet performance targets and renew annually (including paying the program fee). The designation can be lost if the company doesn’t maintain requirements or lapses in renewal. Individual certifications usually expire every year or two and require an individual to take renewal training or exams to stay current, but they are maintained by the individual and can move with them from one employer to another. In essence, the Solutions Partner designation is tied to the partner company’s ongoing business performance and Microsoft partnership status, whereas certifications are tied to professional development of employees.
• Purpose: The Solutions Partner designations align with Microsoft’s go-to-market solution areas and are intended to identify partners who can deliver broadly in those high-demand areas. They help Microsoft and customers quickly find a qualified partner for a project (for example, if a customer needs a Security solution, they look for a Solutions Partner for Security). Individual certifications, meanwhile, support the partner’s journey by ensuring the technical staff have the necessary skills; they are a building block in the partner capability score. They also serve the broader IT industry by standardizing skill verification for professionals. But an individual cert alone doesn’t confer any direct partnership benefits – it’s the accumulation of certified individuals, successful projects, and satisfied customers that earns a company Microsoft’s designation.

In summary, think of a Solutions Partner designation as a “credential for a company”, demonstrating that the firm as a whole has “broad technical capabilities, a dedication to skilling, and a proven ability to deliver successful solutions” in a given area. In contrast, an individual Microsoft certification is a credential for an individual, proving that person’s knowledge of a specific Microsoft technology or role. Both are valuable, but they operate at different levels: one enhances the company’s stature in Microsoft’s ecosystem, and the other enhances an employee’s qualifications. The two work hand-in-hand – having more certified individuals helps the company achieve the partner designation, and achieving the partner designation provides a framework and incentive for companies to invest in training their people.

Application Process and Scoring Timeline

Becoming a Solutions Partner is a process tightly integrated with Microsoft’s Partner Center system and the Partner Capability Score tracking. There isn’t a traditional “application form” that you fill out and wait for approval; instead, you qualify by meeting the scoring requirements, and then you confirm and accept the designation (including paying the fee) once eligible. Here’s how the process and timeline works:

• Joining the Partner Program: First, a company must be enrolled in the Microsoft Cloud Partner Program (formerly MPN). This involves creating a Partner Center account, getting your organization verified, and agreeing to program terms – essentially becoming a Microsoft partner at the base level. Many partners start by purchasing a partner benefits package or Action Pack (a bundle of software licenses and support) even before attaining any designation, but this is optional. Once you’re in the program, you can pursue the Solutions Partner designations.
• Tracking the Partner Capability Score: Microsoft provides a real-time dashboard in Partner Center that shows your current score in each solution area and how it’s calculated. This data updates regularly as you earn certifications, add customers, or your customers’ usage grows. Performance and customer success data typically refresh monthly (by around the 20th of each month), since they rely on usage/consumption reporting. Skilling updates (new exam passes, etc.) are usually faster, often reflected within a week or two of certification completion. As you approach the targets, you can see exactly which metrics have or haven’t met the minimum 1-point requirement.
• Achieving the Requirements: You can achieve the required 70 points at any time during the year – there is no fixed schedule or deadline to apply; it’s a rolling attainment. The moment your Partner Capability Score meets or exceeds 70 (and you have >=1 point in each category), you become eligible for the Solutions Partner designation in that area. Microsoft’s systems will recognize this achievement automatically. If you were a legacy Gold/Silver competency partner during the October 2022 transition, Microsoft actually automatically granted the new designation on the launch date if you met criteria, to ensure continuity. For new partners, or those reaching the target later, you don’t get the badge until you take action to enroll in the designation.
• Applying/Accepting the Designation: Once eligible, the partner’s admin needs to go into Partner Center and opt in or “purchase” the Solutions Partner designation. The designation itself comes with an annual fee (roughly US $4,730, equivalent to the old Gold competency fee). When you select the designation, you’ll be prompted to pay this fee (pro-rated depending on your renewal cycle) and activate the benefits. Essentially, this is like purchasing the “Solutions Partner benefits package” for that designation. If you already paid for one designation, additional ones in the same membership year typically don’t require extra fees – you pay once per year for the program’s top benefits, and you can earn multiple badges.
• Timeline Expectations: Many partners want to know how long it takes to achieve a designation. This varies widely based on your starting point. For a new partner starting from scratch, it could take several months to a year or more of effort: you need time to get a few people certified, to win some customer projects, and to accumulate usage growth. Microsoft provides a “partner capability score simulator” to help plan this timeline – you can forecast, for example, that “if I certify 2 more people and add 3 new customers in the next 6 months, I’ll reach 70 points”. Some smaller partners focusing on one area have reported achieving the requirements in as little as 3–6 months with focused effort, especially on the skilling side, whereas others might take longer if customer metrics are the bottleneck. The program is designed to be achievable for committed partners of all sizes, but it does emphasize growth – if you remain static (no new customers, no growth), you likely won’t reach or maintain 70 points.
• Receiving the Designation and Badges: Once you opt in and pay, Microsoft will officially award the designation. You’ll see your Solutions Partner badge available in the Partner Center’s logo builder to download for marketing use. Your partner listing on Microsoft’s websites will update to show the Solutions Partner designation within a short time. There is no lengthy manual vetting at this stage because the vetting is essentially the point system itself – it’s based on hard data.
• Anniversary and Renewal: The designation runs on an annual cycle tied to your anniversary date (often the date you initially enrolled or the new program launch date in 2022). Each year, you must renew by paying the annual fee again and, crucially, you must still meet the requirements at that time to re-attain the designation. Microsoft typically gives a grace period if your score drops slightly just before renewal – for example, if you dipped below 70, you might have until the renewal date to improve it. If you cannot meet the criteria, you risk not being able to renew that designation (though you remain a basic partner and could possibly choose a lower-tier benefits package to retain some software benefits). It’s expected that partners maintain continuous performance: the Partner Capability Score is continuously updated, so you should monitor it year-round and address any declines (like expiring certifications or loss of a customer) proactively. Many metrics are trailing 12-month based, so consistent effort is needed to keep the numbers up.
• Maintaining and Improving Score: During the year, if you achieve 70 points and get the designation, you’ll want to continue improving your score, both to cushion against fluctuations and to prepare for future changes (Microsoft can raise targets or adjust metrics over time). The scoring model may also evolve; for instance, Microsoft might introduce new certifications or change thresholds as technologies change. It’s wise to keep skilling new staff (to replace expiring certs or people who leave), continue acquiring new customers, and invest in customer success so that your designation is secure. Also note that partners must have appropriate associations (CPOR, PAL, etc.) set in Partner Center for customer deployments – the system only counts customers where you are properly linked as the partner of record. A part of the process is thus administrative: ensuring all your customer engagements are tagged so that Microsoft sees the revenue/usage and credits it to your score.

In terms of timeline expectations, from the moment you hit the targets to the moment you have the badge is usually very quick – the monthly score refresh might be the longest wait. If, say, you closed a qualifying project on the 5th of the month, that data might not reflect until the 20th or so; but if you just got a certification, it could show up within days. Once the score in Partner Center shows 70+/100 with all categories non-zero, you can essentially immediately take the action to attain the designation. There is no separate committee or lengthy approval beyond the automated scoring. This is a big improvement over some legacy programs that required documentation or case studies – now it’s all metrics-driven.

Finally, after you have the designation, Microsoft’s advice is to use the benefits fully and keep an eye on the Insights reports in Partner Center which explain how your score is calculated and where you might improve. Also, be aware of fiscal year timelines: Microsoft often updates incentive eligibility or benefit changes at the start of a new fiscal year (July), so ensuring you attain designations before those dates can maximize your returns (for example, certain incentives from FY2026 onward require designations).

SMB vs. Enterprise Paths for Azure Designations

Microsoft recognizes that partners serve different customer segments – some primarily cater to small and mid-sized businesses (SMB), while others focus on large enterprises. To level the playing field, Microsoft introduced two attainment paths for several Solutions Partner designations, particularly in Azure solution areas: an “Enterprise” path and an “SMB” path. Both paths lead to the same designation and benefits; they simply adjust the criteria to be achievable relative to the partner’s customer profile. Here’s a comparison of these paths and how they work:

• Enterprise Path: The enterprise track is intended for partners who deal with larger customers (corporate and enterprise accounts). The thresholds in this path are higher in absolute terms. For example, under the initial enterprise criteria for Azure designations, a “net new customer” was defined as a customer spending at least $1,000 USD per month in Azure (Azure Consumed Revenue). Similarly, for Modern Work, a new customer meant >300 licenses deployed. The enterprise path expects partners to drive sizable deployments – typically, enterprise-focused partners have fewer, but very high-value, customers. Additionally, the skilling requirements on the enterprise path often require a higher number of certified individuals (as mentioned earlier, e.g. 4 associates + 2 experts instead of the SMB’s 2+1) because larger partners are expected to have bigger teams. Enterprise path metrics also consider that an enterprise partner’s customer base may not grow in count quickly, so while the thresholds are high, you might only need a handful of big wins (e.g. 5 enterprise customers could max out the performance score, rather than needing 10+ small ones).
• SMB Path: The SMB track is tailored to partners primarily serving small and medium customers. These partners might sign many smaller deals rather than a few big ones. Therefore, the criteria lower the bar on what counts and often allow volume to compensate for value. For instance, for Azure solution areas, Microsoft reduced the Azure consumption threshold for a customer to count as “net new” from $1,000 to $500 per month on the SMB path. That means even smaller Azure projects (common in SMB) will give the partner credit. In Modern Work, an SMB-path partner gets credit for adding tenants with, say, 20 or 50 seats, whereas those wouldn’t count on the enterprise metric which looks for >300 seats. The number of customers required may be higher (because each is smaller): e.g. 10 SMB customers at 2 points each to reach 20 points in performance, vs 5 enterprise customers at 4 points each. The skilling requirements are also scaled down – an SMB partner can achieve full skilling points with roughly half the number of certified people compared to enterprise path. Microsoft also often gives SMB path credit for some “intermediate” certifications that are more foundational, acknowledging that a smaller partner may not have many expert-level consultants yet.
• Automatic Path Determination: Partners do not explicitly choose a path; Microsoft’s system will assess your partner profile and calculate your score on both paths in parallel, then whichever score is higher is used for qualification. The criteria for being considered an “SMB partner” vs “Enterprise partner” hinge on your customer mix. According to Microsoft’s definition, as of early 2025 an SMB-path partner is generally one with less than $1M in Azure consumption over the last year and with 80% or more of their customers categorized as SMB/SMC (small, medium, or corporate). Conversely, if over 20% of your customers are enterprise segment or you have >$1M ACR, you fall into the Enterprise category. These aren’t hard rules to force you into one bucket – they mainly ensure that a predominantly SMB-serving partner can use the SMB scoring. In fact, a single partner might earn points via both sets of criteria: for example, you might have a few enterprise clients and many SMB clients; Microsoft will evaluate both scenarios and credit you the optimal score. This automatic evaluation means you don’t have to worry about flipping a switch; simply pursue customers and the score will favor the path that benefits you.
• Outcome is the Same: Whether you qualify via the SMB path or the Enterprise path, the designation you earn is identical, and so are the benefits. There is no “SMB version” of the badge – a Solutions Partner is a Solutions Partner. The dual-path system is purely about making the achievement attainable and fair. Microsoft essentially doubled the ways to score points: e.g., if a customer has 250 seats (which qualifies as SMB) that you added, you get SMB path points; if another customer has 500 seats, that might count under enterprise metric. The highest combination of points wins for each metric category.
• Example – Azure Infrastructure: Consider two Azure partners: Partner A manages mostly small clients (each consuming ~$600/month on Azure), while Partner B manages a few large clients (each consuming $50k/month). Under the old single criteria, Partner A might struggle to show growth since none of their clients hit the $1k threshold, whereas Partner B would easily count a few and get points. With SMB path, Partner A’s clients now count (lower threshold), so if Partner A adds 5 new small clients (each ~$600 ACR), they could get full 20 points on SMB performance. Partner B might add just 1 huge client to get points, but maybe they don’t add as many net new logos; still, they’ll get credit on enterprise metrics. In the end, both can reach 70 via different mixes. Microsoft’s scoring engine ensures partners serving the long tail of smaller customers are not penalized – their incremental wins are recognized proportionally.
• Status as of 2025: Initially, the SMB path was rolled out for Modern Work and Business Applications (around late 2022). In February 2025, Microsoft announced the SMB path for the Azure solution areas (Data & AI, Digital & App Innovation, Infrastructure) is now active. This was a response to partner feedback to better align with those focused on SMB customers. Additionally, Microsoft has indicated that an SMB path for Security is in progress and expected later in 2025. The goal is for all major solution designations to have this flexibility. It’s worth noting that the SMB path still requires 70 points total – that hasn’t changed – and both SMB and Enterprise partners must demonstrate capabilities across performance, skilling, and customer success (with at least 1 point in each sub-metric). The difference is purely in the scale of metrics used to award those points.

In practice, the SMB vs Enterprise distinction has made it more feasible for regional partners, boutique consultancies, and others who thrive on smaller projects to earn the Solutions Partner status. A partner should focus on their business strengths: if you serve mostly SMB, you’ll naturally accumulate points through that path. If you have some large accounts, those will boost your enterprise metrics. Microsoft’s system ensures your work is recognized proportionately, regardless of customer size, so you can choose the path (implicitly) that aligns with your strategy and still achieve the designation. This dual-path approach reflects Microsoft’s commitment that the new partner program remains inclusive and “designed to ensure that designations are achievable regardless of organization size”.

“Solutions Partner with Certified Software” Designation and ISV Success

In addition to the six solution area designations for service-oriented partners, Microsoft has introduced a special designation for software publishers: “Solutions Partner with Certified Software.” This is aimed at Independent Software Vendors (ISVs) – partners who build and sell their own software solutions that integrate with Microsoft’s platforms. The Solutions Partner with certified software designation is essentially a mark of quality and compatibility for an ISV’s product, complementing the partner’s organizational status. Here’s an overview of what this designation means and how it connects to Microsoft’s ISV Success Program:

What is “Solutions Partner with Certified Software”? – It is a designation awarded to a partner for a specific software solution that the partner has developed, once that solution meets certain criteria for technical excellence and customer success on the Microsoft Cloud. In other words, while the regular Solutions Partner designations validate a partner’s services capability, the certified software designation validates a partner’s product. Becoming a Solutions Partner with certified software signifies that your software has passed technical reviews for interoperability with Microsoft’s cloud and has proven customer outcomes. Microsoft introduced this program to help customers more easily identify ISV solutions that are trustworthy and well-integrated. For the partner, it’s a way to differentiate their product in Microsoft’s commercial marketplace and gain customer trust.

Eligibility and Criteria: To attain a certified software designation, an ISV must first be a member of the Microsoft Cloud Partner Program (i.e., be a Microsoft partner) and typically also achieve a base Solutions Partner designation in a relevant area. Then, the ISV’s software solution needs to fulfill specific requirements, which fall into a few categories:

• Commercial Marketplace Readiness: The solution must be published as an offer in Microsoft’s commercial marketplace (Azure Marketplace or AppSource) and ideally be transactable there (meaning customers can directly purchase or trial it through the marketplace). It should also meet IP co-sell eligibility, which implies the solution is validated for Microsoft’s co-sell program (Microsoft sellers can co-sell it). Essentially, the product has to be “market-ready” in Microsoft’s ecosystem.
• Technical Interoperability: The solution undergoes a technical review to ensure it follows Microsoft’s best practices and integrates properly with Microsoft cloud services. For example, if it’s a software that works with Azure, does it adhere to Azure well-architected guidelines? If it’s built on Dynamics 365 or Teams, does it use the supported APIs and meet security/compliance standards? This review might include checks like the software’s architecture, security, and performance on Azure. It is often a self-attestation plus possibly some auditing – Microsoft wants to ensure the software “plays nice” with its platforms. A key point is that the certification is based on interoperability and is point-in-time – it’s not an endorsement of every aspect of the software, but a confirmation that it meets the bar for working with Microsoft products as of the time of review.
• Customer Success and Performance: The ISV must demonstrate a track record of customers using the solution successfully. Microsoft looks at marketplace performance (e.g. number of deployments or trials, customer ratings) and other evidence of customer value. They might require a minimum number of customer ratings (for instance, an average rating of 4+ stars with 15 or more reviews in marketplace might be a criterion – early info suggested something along those lines for some areas). They also consider if the solution has driven tangible outcomes (case studies or metrics proving that it solves the intended problem). Essentially, the ISV has to prove that not only can they list software, but that customers are actually adopting it and finding success.

There are two pathways for certified software designations: one aligned to the standard solution areas and one aligned to Industry-specific AI solutions. For example, an ISV solution that is a security software would pursue “Solutions Partner with certified software for Security,” while an industry-focused AI solution (say, AI for Healthcare) might pursue an Industry AI designation. In the context of the question, we focus on the solution area path, which covers Azure, Business Applications, Modern Work, and Security as categories of certified software designations. An ISV could potentially earn multiple such designations if they have multiple products or a product that spans categories (e.g., a solution that integrates with both Azure and Modern Work could theoretically get both badges).

Connection to ISVs: This designation is explicitly targeted at ISVs – companies whose primary business is developing software (as opposed to service providers or resellers). Microsoft often uses the term “Solutions Partner” generally for partners in the program, but here “Solutions Partner with certified software” indicates that the partner is offering a software solution that has been certified. It provides a way for ISVs to showcase their software’s quality in parallel to showcasing their own technical competencies. In fact, Microsoft has started referring to these as distinct partner types. For example, Microsoft’s partner program updates mention “parallel designations for specific partner types, such as Solutions Partner for ISV (with certified software)” to address the ISV scenario separately. So an ISV might hold a Solutions Partner designation in, say, Digital & App Innovation (showing they as a company have Azure app development skills) and additionally earn “Solutions Partner with certified software for Azure” for their SaaS application, showing the app itself is certified.

ISV Success Program Relationship: The ISV Success Program is an initiative by Microsoft to help ISVs build, publish, and grow their apps on the Microsoft Cloud. It provides qualified ISVs with various benefits such as free Azure credits, developer tools, technical consultations, and go-to-market resources (it’s somewhat analogous to an incubator/accelerator for software companies on Azure). As of 2023-2024, Microsoft offered ISV Success in “Build” and “Grow” stages, often as part of the AI Cloud Partner Program benefits package for ISVs. The link between ISV Success and the certified software designation is as follows:

• ISV Success as the On-Ramp: Through the ISV Success program, partners get the support to develop and polish their solutions. They receive guidance on how to meet marketplace requirements, how to align with Microsoft’s best practices, and how to prepare for co-sell. The program provides a lot of the resources needed to eventually achieve the certified software designation. In fact, Microsoft explicitly calls out that after utilizing ISV Success “Build and Publish” benefits, the next step is to “meet criteria for Solutions Partner with Certified Software”, which validates and amplifies the solution in the market. So, one can view ISV Success as Phase 1 (build the solution with Microsoft’s help) and Certified Software designation as Phase 2 (get it certified and go-to-market at scale).
• Benefits and Incentives (Post-Certification): Once an ISV attains the certified software designation, they unlock additional benefits that go beyond ISV Success. According to Microsoft, attaining a certified software designation “unlocks go-to-market, sales, and marketing benefits” aimed at driving demand for the ISV’s solution. For example, the ISV gets a customer-facing badge on their marketplace listing indicating the solution is certified – this can significantly increase customer confidence and click-through. They also receive Microsoft solution play cards, marketing assets, and one-on-one consultation (marketing concierge) to help promote the solution. These are benefits specific to having a certified solution, layered on top of any core partner benefits. Notably, one incentive is that certified software partners qualify for certain Azure ISV-related incentives, like Azure credits or funds for customer migrations/innovations involving the ISV’s solution. For instance, if your software helps customers use Azure, Microsoft might fund pilot projects (via Azure Migrate and Modernize or Azure Innovate offers) when you have the certified badge.
• Top Tier ISV Benefits and Co-Sell: Microsoft has something called “Top Tier” benefits for ISVs, which include access to partner-reported Azure consumption recognition (so Microsoft sellers get credit for selling your SaaS, motivating them to co-sell it) and enhanced listing with Microsoft sellers internally. These top-tier perks kicked in from July 1, 2024, for ISVs who attained certain certified software designations. The ISV Success Program in its basic form might provide Azure credits and guidance, but the certified software designation plugs the ISV into Microsoft’s sales engine more directly – it flags to Microsoft field teams that this solution is vetted and they should consider recommending it. So, ISV Success helps you build a good solution; certified software status helps you sell it through Microsoft channels.

In summary, the Solutions Partner with certified software designation is a new layer in Microsoft’s Cloud Partner Program that specifically elevates ISVs. It is closely related to the ISV Success Program: you can think of ISV Success as the journey of enabling an ISV (providing technical and business resources), and the certified software designation as the destination where the ISV’s product is formally recognized and promoted by Microsoft. An ISV in the program might start by joining ISV Success (which as of 2025 might require purchasing an ISV Success package similar to how service partners purchase partner benefits), use those benefits to get their app ready, list it on Azure Marketplace, gain some customers and refine it, and then apply for the certified software designation when they meet the criteria (transactable offer, technical validation, customer success). Once certified, the ISV gains a badge that signals quality to customers and unlocks deeper go-to-market integration with Microsoft (like co-sell support and special marketing initiatives).

For ISVs, this path is extremely valuable: it provides a clear goalpost (certification) to work towards, with Microsoft’s help along the way via ISV Success. It essentially parallels the experience that service partners have (where they get a Solutions Partner badge for their service excellence) by giving software providers a comparable badge for their product excellence. Microsoft’s messaging to ISVs is that by achieving Solutions Partner with certified software, you “differentiate your software solution in areas of high customer demand, increase discoverability in the marketplace, connect with more customers, and accelerate your revenue”. And because this designation is now generally available as of mid-2023, Microsoft is encouraging ISVs to also consider joining the ISV Success Program if they haven’t, since that’s the route to both build a great product and meet the certification bar.

In essence, Solutions Partner with certified software is to ISVs what the six solution area designations are to service partners – a mark of quality and capability – and the ISV Success Program is the enablement pipeline that helps ISVs get there (and beyond). Together, they form the ISV-facing branch of the Microsoft AI Cloud Partner Program, ensuring that software makers can showcase their innovations with Microsoft’s endorsement and tap into Microsoft’s vast customer and seller network to grow their business.