Every shortlist for a Dynamics 365 project looks the same by the second round. Three or four firms, each with the Solutions Partner for Business Applications logo on the cover slide, each with a case study deck, each promising a senior team. The logo makes them look interchangeable, and that’s exactly the problem. It tells you a firm cleared Microsoft’s bar at a program level. It says nothing about whether the people who show up on your project have ever migrated eight years of open AP from a legacy ERP, rebuilt an intercompany posting setup across four legal entities, or survived a month-end close on a system they configured themselves.
If you’re the CIO or CFO signing the statement of work, the badge is where your diligence starts. It shouldn’t be where it ends.
What the Dynamics 365 Badge Actually Certifies?
Microsoft’s Solutions Partner designations run on a points model. A partner needs a partner capability score of at least 70 out of 100 in a solution area, with points spread across three categories: performance (net customer adds), skilling (certified people), and customer success (usage growth and deployments). They also need at least one point in every metric, and they have to hit that bar on some day inside the qualification window.
Read that carefully and you’ll see what it measures. It measures volume and momentum across the partner’s whole book of business. A firm can qualify on the strength of dozens of small Sales or Customer Service deployments and still have shipped very few finance implementations. It can earn its skilling points from consultants who’ve since left. And because the score is calculated across the solution area, it doesn’t separate Business Central work from Finance and Operations work, or a 40-user distributor from a 2,000-user manufacturer.
None of this makes the designation worthless. It filters out firms that have no real Microsoft practice at all, and that’s a genuine service when you’re sorting through a long list. But it’s a floor, not a fit test. Treat it like a professional license: necessary, and nowhere near sufficient.
Specializations narrow things a little. They require additional evidence of delivery in a specific workload, and they’re worth asking about. Still, a specialization tells you the firm has done the work somewhere, for someone. You need to know whether it has done your work.
Scope Evidence Beats Logos Every Time
Most selection processes compare firms on the wrong axis. They score company-level attributes: headcount, years in business, designations, a Dynamics 365 logo wall of past clients. Then they’re surprised when the project stalls on something none of those attributes predicted, like a warehouse integration nobody on the partner side had built before.
A better approach is to compare dynamics 365 implementation partners on scope evidence. Before you look at anyone’s slides, write down the five or six things that make your project hard. For most mid-size and enterprise buyers, that list looks something like this:
1. Module mix:
General ledger and AP are table stakes. Production control, advanced warehousing, project accounting or revenue recognition are where experience shows.
2. Legal entity and currency structure:
Intercompany eliminations and multi-currency consolidation break more go-lives than anything in the core ledger.
3. Data volume and history:
How many years of transactions, how many open items, how dirty the source data is.
4. Integration landscape:
Your WMS, your e-commerce platform, your payroll provider, your bank feeds, and whichever homegrown system nobody wants to talk about.
5. ISV add-ons:
Which third-party apps you’ll depend on, and who supports them after go-live.
6. Regulatory and industry constraints:
Lot traceability, FDA or SOX controls, e-invoicing mandates in the countries you operate in.
Now ask every candidate the same question: show us a project that matched at least four of these. Not a case study written by marketing. A project, with a customer you can call.
This reframes the whole conversation. You stop asking “are you good?” and start asking “have you done this, specifically?” A firm that’s been honest with itself will tell you where it’s thin. A firm that hasn’t will tell you every project is different and their methodology handles it. That answer is your first data point.
How to Run a Reference Check That Tells You Something?
Reference calls are usually wasted. The partner picks a happy executive sponsor who went live three months ago, the sponsor says nice things, and everyone moves on. You can do much better with a little structure.
Start with the selection rules. Ask for references from Dynamics 365 projects that went live at least 12 months ago, because the first year is when deferred problems surface: the reports nobody tested, the year-end close, the audit. Ask for projects of comparable scope and module mix, ideally in your industry. And insist on talking to someone who uses the system, not just the person who signed the contract. The customer’s financial controller or AP manager will tell you things the CFO never saw.
Then ask questions that have specific answers:
1.Who from the partner was actually on the project?
Get names. Compare them with the names in your proposal. If none overlap with the team that delivered the reference, the reference is about a different firm.
2. How did data migration go?
Ask how many trial migrations they ran, who owned data cleansing, and whether opening balances reconciled on the first try.
3. What happened at cutover?
Was there a parallel run? How long did the business operate on workarounds?
4. How long was hypercare, and was it enough?
Ask whether the partner’s people stayed engaged after go-live or handed off to a support desk within two weeks.
5. How many change orders were there, and why?
A few are normal. A pattern of change orders for things that should’ve been in the original scope tells you how the partner estimates.
6. Which ISV add-ons did you end up with?
And would you choose them again?
7. Would you hire this exact team again?
Not the firm. The team.
Listen for hesitation more than for praise. “It was a learning experience for everyone” is not a compliment.
Check the People, Not the Company
Firms don’t configure posting groups. People do. So the most useful diligence you can run is on the named consultants in the proposal.
Ask for the specific people who’ll fill the solution architect, lead functional and technical lead roles, and ask for their Microsoft certification transcripts. Microsoft publishes these as verifiable credentials, so you’re not relying on a resume line. For Business Central work, the functional baseline is MB-800, the Business Central Functional Consultant exam. For Finance and Operations, look for MB-310 on the finance side and MB-330 if supply chain management is in scope. Microsoft’s associate certifications expire annually and renew through a free online assessment, so a current certification tells you someone has kept up with the product, not just passed an exam years ago.
Certifications aren’t experience, of course. Someone can pass MB-310 and still never have run a live period-end close. So pair the transcript with a short working session. Give the proposed lead consultant a real problem from your business, such as how they’d handle your intercompany structure, and watch how they reason through it. Fifteen minutes of that is worth more than a 60-slide methodology deck.
Finally, get named resources written into the contract, along with a clause covering substitution. If a key person leaves, you should get approval rights over the replacement. Bait-and-switch staffing is the oldest complaint in ERP services, and it’s preventable on paper.
FastTrack Is a Useful Signal, With Limits
Microsoft’s FastTrack program puts Microsoft solution architects alongside your partner for reviews such as the solution blueprint and go-live readiness check. For a large Finance and Operations rollout, that’s a meaningful second set of eyes.
Eligibility has two halves. The customer has to meet a minimum annual Dynamics 365 license spend on eligible new deployments, and the partner has to qualify. Per Microsoft’s FastTrack eligibility criteria, a qualified partner is a Solutions Partner for Business Applications with at least two eligible customer deployments of the matching type, so finance and operations projects need finance and operations deployments. The partner team also has to complete Success by Design training and a knowledge check before the project starts.
That makes FastTrack qualification a slightly sharper signal than the designation alone, because it’s tied to completed deployments of the right app family. Ask candidates directly whether they qualify, and how many of those deployments they’ve done.
Two caveats. First, Business Central isn’t on Microsoft’s current list of FastTrack-eligible apps, so if that’s your platform, this signal doesn’t apply and you should lean harder on references. Second, two deployments is a low bar. It proves the firm has done it; it doesn’t prove they’ve done it at your scale.
Red Flags Worth Walking Away From
- Some warning signs show up early, if you’re looking for them:
- The proposal names roles but not people, and the firm resists naming them before signature.
- Every reference went live less than six months ago.
- The partner can’t say which ISV add-ons it would recommend, or recommends its own add-on for everything.
- The estimate has a single line for data migration with no assumptions attached.
- Hypercare is two weeks, fixed, regardless of your go-live date relative to month-end.
- Nobody asks about your chart of accounts, your entity structure or your close calendar in the discovery sessions.
Any one of these is a conversation. Two or three together is a pattern.
A Short Checklist Before You Sign
Here’s the version to hand your selection committee:
- Confirm the Solutions Partner designation and any relevant specialization, then move on.
- Score each candidate on scope evidence against your own list of hard requirements.
- Run at least two reference calls per finalist, with projects live 12 months or more, including someone from the customer’s finance team.
- Verify the named consultants’ current Microsoft certifications and hold a working session with the lead.
- Ask about FastTrack qualification if you’re on Finance and Operations
- Write named resources and substitution approval into the contract.
The Dynamics 365 badge got these firms onto your shortlist. Your reference checks decide which one gets the project. Start with your own list of what makes this implementation hard, and make every candidate prove they’ve handled those exact problems before, with customers you can call and consultants you can name. Then give the final say to the person who’ll close the books on the new system in its first year-end, because they’re the one who’ll live with whichever partner you pick long after the project team has moved on.
Also Read :- How AI Turns Procurement Data Into Actionable Business Insights?
