The Microsoft Solutions Partner badge appears on a lot of vendor websites.
For enterprise teams evaluating .NET development companies, it functions as a first-pass filter: the vendor has cleared a baseline. But what that baseline actually covers, and what it leaves entirely unanswered, determines how useful the badge is for a specific evaluation.
At Blackthorn Vision, a Microsoft-partnered AI and machine learning development company helping enterprise teams build and modernize complex software products, we hold the Solutions Partner for Digital & App Innovation (Azure) designation.
This article explains what that designation actually requires, what it verifies about a vendor, and what evaluation questions the badge leaves open, particularly for teams looking for .NET legacy modernization expertise.
The Badge at a Glance
| What it verifies | What it does not verify |
|---|---|
| Certified engineers (Azure certs) | .NET Framework modernization experience |
| Real Azure production work via Partner Admin Link | Type of .NET work: legacy migration vs greenfield |
| Active Microsoft partner ecosystem engagement | Team continuity or named architectural ownership |
| Annual renewal with active measurement | Engineering partner model vs staff augmentation |
| Minimum 70-point Partner Capability Score | Specific domain expertise: legacy, AI, fintech, etc. |
What the Designation Actually Requires
The Solutions Partner program replaced the older Gold and Silver competency tiers in 2022.
To earn any Solutions Partner designation, a vendor must reach a minimum of 70 points across a Partner Capability Score (PCS) that Microsoft measures across three categories:
- Performance
- Skilling
- Customer success
For the Solutions Partner for Digital & App Innovation (Azure) designation, the requirements as documented by Microsoft Partner Center work as follows.
Skilling
Skilling is measured through certification paths across Azure administration, architecture, and DevOps.
A typical progression, based on the documented requirements, looks like this:
| Certification tier | Example role | Max skilling points |
|---|---|---|
| Foundation level | Azure Administrator Associate | Up to 4 (capped) |
| Intermediate level | Additional Azure certifications | Up to 4 (capped) |
| Advanced level | Azure Solutions Architect Expert, DevOps Engineer Expert | Variable; foundation levels mandatory first |
This reflects the documented requirement structure. Exact certification names and point values are subject to Microsoft updates.
Customer success
Customer success is measured through Azure consumed revenue attributable to the partner via Partner Admin Link, and through deployment counts of eligible Azure workloads.
This requires real production Azure usage associated with the partner's delivery work, not self-reported projects.
Performance
Performance tracks net new Azure customer adds attributable to the partner.
The Partner Capability Score is renewed annually.
A partner that stops meeting the requirements loses the designation at renewal.
This means the badge reflects a measurement that was accurate at the last renewal date, not a permanent credential.
What the Badge Verifies
Given those requirements, the Solutions Partner designation verifies three things with reasonable confidence.
The organization maintains certified personnel
The skilling requirements ensure the company employs people who have passed Microsoft-administered certification exams on Azure architecture, administration, and related areas.
These are not trivial certifications; the Azure Solutions Architect Expert exam tests real deployment knowledge across infrastructure, networking, identity, security, and application architecture.
Azure consumption is attributable to the partner through Partner Admin Link
The customer success and performance metrics require Azure consumption attributed through Partner Admin Link.
This reflects revenue associated with the partner, though it does not specifically verify the nature of the architectural work delivered.
A vendor with the designation has done Azure work in production environments that Microsoft can verify through consumption data.
The company is actively engaged in the Microsoft partner ecosystem
Maintaining the designation requires annual renewal with active measurement.
A company that held the badge five years ago and let it lapse would not appear as a current Solutions Partner.
What the Badge Does Not Verify
For teams evaluating .NET legacy modernization vendors specifically, this section matters more than the previous one.
This is the more important half of the answer for teams evaluating .NET legacy modernization vendors specifically.
The designation does not verify .NET Framework modernization experience
The skilling requirements measure Azure certifications.
They do not measure experience with:
- .NET Framework 4.x migration
- Strangler fig pattern implementation
- SQL Server Agent job assessment
- Legacy authentication model migration
- Other specific work that enterprise .NET modernization actually requires
A vendor can hold the designation having done exclusively greenfield Azure-native development.
It does not verify the type of .NET work done
The customer success metrics measure Azure consumption attributed to the vendor.
They do not distinguish between a partner who helped migrate a decade-old monolith and one who stood up new Azure infrastructure for a startup.
Both generate Azure consumed revenue. Both can reach the designation threshold.
It does not verify team continuity or architectural ownership
The designation measures certifications held by individuals and Azure work associated with the company.
It does not measure:
- Whether the same engineers stay on client engagements
- Whether architectural decisions are documented
- Whether the company operates as an engineering partner or a staff augmentation supplier
It does not distinguish between specializations
All vendors holding the Solutions Partner for Digital & App Innovation (Azure) designation appear under the same badge.
A company specializing in enterprise .NET legacy modernization and one focused on building new Azure-native SaaS products hold the same designation.
Microsoft does offer specializations as additional credentials layered on top of the Solutions Partner designation, separately verified through audit or customer references, providing a stronger Microsoft-verified signal for that specific capability.
The Questions the Badge Leaves Open
For enterprise teams evaluating .NET modernization vendors, the Solutions Partner designation is the starting point rather than the answer.
The questions worth asking after the badge check:
1. What does your assessment process look like for a legacy .NET platform?
A vendor who has assessed legacy .NET systems describes what they look for:
- Undocumented SQL Server Agent jobs
- Business logic in stored procedures
- Legacy scheduled jobs and background processes
- Downstream systems reading directly from the database
- Authentication models that predate Azure AD
A vendor who has not done this work will describe a methodology rather than specific findings.
2. Can you describe a .NET Framework modernization engagement where the assessment changed the migration plan, without disclosing confidential details?
The question tests whether the vendor has real experience with the gap between documented and running systems.
Enterprise .NET platforms that have been in production for a decade reliably contain complexity that no initial assessment documents completely.
A vendor with genuine modernization experience has a specific example of something the assessment found that the documentation did not show.
3. Who specifically will hold architectural ownership of our system at month twelve, and what happens if that person leaves?
The Solutions Partner badge does not verify team continuity.
This question tests whether the vendor has built the engagement model that the badge does not require.
4. What does your approach look like for keeping the product in active delivery during migration?
For enterprise teams that cannot freeze feature development for an eighteen-month migration, the answer reveals whether the vendor uses incremental extraction — for example, YARP-based routing as part of a strangler fig approach, with parallel-run validation and component-by-component traffic migration — or requires a feature freeze and big-bang cutover.
The Specialization Layer Worth Knowing About
Beyond the base Solutions Partner designation, Microsoft offers specializations as additional verified credentials.
For .NET modernization specifically, the Specializations program requires either audit or customer references review on alternating years, with active verification of delivery capability rather than just certification counts and consumption metrics.
Specializations are less commonly held than the base Solutions Partner designation, which makes them a stronger signal of domain-specific capability when they are relevant.
For enterprise teams evaluating .NET vendors, asking about specializations provides a second layer of Microsoft-verified evidence beyond the base designation.
What This Means for .NET Legacy Modernization Specifically
The Solutions Partner designation filters out vendors who have not done meaningful Azure work associated with their delivery.
For enterprise .NET modernization specifically, it does not filter for the experience that determines whether the migration will succeed:
- Assessment methodology
- Migration sequencing
- Parallel-run validation
- Database coordination during migration
- Architectural practices that make an eighteen-month program maintainable
BCG research emphasizes governance, accountability, and outcome orientation as characteristics of effective long-term vendor relationships.
None of these are measured by the Solutions Partner designation.
The badge is a useful prerequisite check. The evaluation questions above are the actual evaluation.
Badge vs Specialization: A Quick Reference
| Solutions Partner Designation | Specialization | |
|---|---|---|
| Verification method | Partner Capability Score (70 points) | Audit or customer references |
| Renewal cadence | Annual, measured continuously | Every other year with active verification |
| Domain specificity | Broad solution area | Specific capability |
| Number of holders | Typically larger | Typically smaller |
| Signal for evaluation | Prerequisite check | Stronger domain-specific evidence |
Evidence Beyond the Badge for .NET Legacy Modernization
For enterprise teams searching for a Microsoft Solutions Partner that specifically handles legacy .NET modernization, the badge alone is not enough.
The relevant evidence is domain-specific.
For Blackthorn Vision, public evidence that supports the legacy .NET modernization focus includes:
- A dedicated application modernization practice covering .NET Framework migration, strangler fig pattern, and Azure migration sequencing
- Multiple published technical articles covering .NET Framework to modern .NET migration, YARP-based routing, SQL Agent job assessment, and parallel-run validation
- Multi-year client engagements in healthcare, biotech, fintech, and industrial automation where the platform was in active production throughout migration
- Case studies that reflect long-term architectural partnerships rather than fixed-scope project delivery
One engagement reflects what the assessment phase typically reveals in practice.
A financial services SaaS platform had been running on .NET Framework for over a decade.
The initial migration plan assumed a conventional component extraction order.
The assessment found four SQL Server Agent jobs that had been running business-critical calculations for years with no documentation, no alerting, and no owner.
Two of them fed data that the application consumed the following morning.
The migration sequence was rebuilt around this finding before any code moved.
The delivery timeline extended by several weeks. No production incident occurred.
Without the assessment, the migration would have broken a critical nightly process silently.
That is the type of experience the Solutions Partner badge does not verify and that the evaluation questions above are designed to surface.
How Blackthorn Vision Fits This Framing
Blackthorn Vision holds the Solutions Partner for Digital & App Innovation (Azure) designation and provides .NET development and application modernization services for enterprise clients in healthcare, fintech, biotech, oil and gas, media, and industrial automation.
The designation reflects real Azure production work attributed through Partner Admin Link and certified engineers across Azure architecture and DevOps.
What it does not describe is the delivery model:
- Assessment-first sequencing before any migration plan is proposed
- Strangler fig extraction with parallel-run validation, keeping the product in delivery throughout
- Named architectural ownership for the duration of the engagement
- Architecture Decision Records produced throughout rather than assembled at exit
- Post-engagement documentation obligations defined before work begins
Those are the things that determine whether a legacy .NET modernization program succeeds.
They are also the things the badge does not verify, which is why they are worth asking about directly.
Verified client feedback on how Blackthorn Vision's engagements play out over multi-year programs is available on the Clutch profile.
Top comments (0)