What does the business analyst do on a Dynamics 365 project?
Most of the job is turning how a business works into something the build team can deliver. You run workshops with finance, sales, service or warehouse staff, draw the current process, and agree what the future process should look like. Microsoft's implementation guidance says to organize these sessions by the level 2 process areas in its business process catalog, and to hold more than one workshop where an area is complex, such as two sales organizations each running their own order to cash.
Fit-to-standard comes first. You walk users through the standard Dynamics 365 process and record where it already meets the need through configuration. Fit-gap follows, after that configuration. It identifies what is still missing and how to fill it: a customization or extension, built with Power Platform or another technology. Microsoft's guidance asks teams to use process maps to show how a change affects connected processes as well as the one being changed. Its stated culture is to adopt wherever possible and adapt only where justified.
User stories, requirements and testing
Workshop notes become backlog items. Microsoft's Azure DevOps template for the business process catalog ties each requirement to a specific process step, which makes coverage easy to check during design and testing. Its discovery workshops are meant to produce a storyline or a set of user stories, and the fit-to-standard workshop produces a refined list of stories plus any gaps, risks or issues.
Testing is where a good analyst earns trust. Microsoft recommends at least one test case for each user story in that template. In practice you write or review those test cases, help key users run them in user acceptance testing, and sort defects into real bugs, missed requirements and change requests. When a developer asks what a requirement meant, you are the person they ask.
How is it different from a functional consultant?
The two roles overlap, and small partners often merge them. Here is the usual split. The business analyst owns the problem: what the business needs, why it needs it, and whether the delivered process meets it. The functional consultant owns the product: setting up parameters, posting profiles, workflows and forms in Dynamics 365, and knowing which standard feature solves which requirement.
A business analyst can do the job with lighter product depth, especially at an end user, where knowing the business counts for more. A functional consultant is expected to configure the system hands-on and is usually billed as the product expert. Many people start as analysts and move into functional consulting once they can configure one app well. The functional vs technical guide covers the next split in the trade.
Who hires, and how do you get in from a business team?
Two kinds of employer hire. Microsoft partners staff analysts onto client projects, where you move between customers and industries. End users, the companies running Dynamics 365, hire analysts into internal IT or transformation teams to own requirements across release waves, enhancements and new rollouts.
The most common route in is from the business side. A finance clerk, customer service lead or planner joins the project as a key user or subject matter expert, sits in workshops, tests the system, and becomes the go-to person for their process. That is already half the analyst job. Formalize it: learn process mapping, write user stories for your own team's change requests, study the free Microsoft Learn content, and take PL-900. Then ask to move into the project or support team.
Pay
USD a year, before tax. D365 Market has no advert row for Dynamics 365 business analysts, so these are BLS OEWS May 2025 national figures moved to 2026 with the Employment Cost Index. They cover generic occupations that include non-Dynamics work, so read them as the nearest match, not as Dynamics 365 pay.
What you need
- CertificationMicrosoft certifications are optional and show product knowledge to employers.
- Process knowledgeHands-on knowledge of one business area, such as order to cash, procure to pay, record to report or case management, is what most hiring managers look for first.
- Process mapping and storiesYou need to draw clear current and future process maps and turn them into requirements and user stories that a developer or consultant can build and test.
- Workshop skillsYou run sessions with mixed groups, keep them to scope, and push back politely when a request only repeats how the legacy system worked.
- PL-900 (optional)Microsoft Certified: Power Platform Fundamentals is a beginner-level certification. Microsoft says it can help you prepare for role-based certifications but is not a prerequisite for any of them.
- EducationBLS says computer systems analysts usually have a bachelor's degree, and some firms hire people with business or liberal arts degrees who have the right skills.
How to get there
- Year 0-1Key user or subject matter expertRepresent your department on a Dynamics 365 project. Attend workshops, test processes, and train colleagues.
- Year 1Learn the basicsWork through Microsoft Learn's free implementation guidance and Power Platform content. Take PL-900 if you want a first credential.
- Year 1-2Junior business analystWrite user stories and test cases, keep process maps current, and take notes in fit-gap workshops led by a senior colleague.
- Year 2-4Business analystLead workshops for one process area, own its backlog, and support user acceptance testing through go-live.
- Year 4+Senior analyst or functional consultantEither lead requirements across several workstreams or build configuration depth in one app and move into functional consulting.
- Year 6+Lead, product owner or architectExperienced analysts often move into product owner, project manager or solution architect roles.
Open now on D365 Market
Questions people ask
Do you need to know how to code to be a Dynamics 365 business analyst?
No. The job is requirements, processes and testing. You do need to understand what configuration, Power Platform and custom development can each do, so your fit-gap decisions make sense to the build team.
Is there a Microsoft certification just for business analysts?
None of the Microsoft Learn pages read for this guide lists a certification for Dynamics 365 business analysts. PL-900 Power Platform Fundamentals is a beginner-level starting point, and analysts who move toward functional work usually take a functional consultant exam for their app next.
What is the difference between fit-to-standard and fit-gap?
Fit-to-standard compares your processes with the standard Dynamics 365 processes and records what configuration already covers. Microsoft says to do fit-gap afterward, to find the remaining gaps and decide how to fill them with customizations or extensions, built with Power Platform or other technologies and solutions.
Should I join a partner or an end user as a business analyst?
A partner gives you more projects and industries in less time, usually with travel and utilization targets. An end user gives you depth in one business and its system over several years. Both count as Dynamics 365 experience.
Can I move from accounting or operations into this role?
Yes. People from finance, customer service or supply chain teams often make the move because they already know the processes. The usual first step is to volunteer as a key user on your employer's Dynamics 365 project.
Sources
- Microsoft Learn: fit-to-standard and fit-gap analysis
- Microsoft Learn: business process catalog deliverables as Azure DevOps work items
- Microsoft Learn: base the implementation lifecycle on processes
- Microsoft Learn: business process guidance, what's new August 2024 (workshops)
- Microsoft Learn: Power Platform Fundamentals certification
- BLS Occupational Outlook Handbook: Computer Systems Analysts
- BLS Occupational Outlook Handbook: Management Analysts
