How to Identify Your Microsoft Dynamics 365 Version

TL;DR

• For Dynamics 365 Sales, Customer Service, and Field Service, select the Settings gear, then About.
• For Dynamics 365 Finance, Supply Chain Management, and Commerce, select Settings, then About and record the application and platform details.
• For Dynamics 365 Business Central, open Help & Support and copy the version from the Troubleshooting section.
• Always check the environment where the issue occurs. Production and sandbox can be on different builds during an update rollout.

Which version-check path should you use?

Use the path that matches your Dynamics 365 application family. “Dynamics 365” covers several products, so there is no single version screen shared by every app. The table below shows the three practical paths and the information to capture from each one.

Dynamics 365 product	Where to check	What to record
Sales, Customer Service, Field Service, and other model-driven apps	Settings gear > About	Full version number shown in the About dialog
Finance, Supply Chain Management, Commerce, and finance and operations apps	Settings > About	Product or application version, platform version, and build details shown
Business Central	Help > Help & Support	Version listed in the Troubleshooting section

The app name alone is not enough for a support case. Record the environment name or URL with the complete version value so the number is tied to the affected production or sandbox instance.

How do you check the version in Sales or Customer Service?

Open the affected Dynamics 365 model-driven app, select the Settings gear in the upper-right corner, and select About. Copy the complete version shown in the dialog. This route applies to apps such as Dynamics 365 Sales, Customer Service, and Field Service running on Microsoft Dataverse.

1. Sign in to the environment where you need to verify the build.
2. Open the Dynamics 365 app.
3. Select the Settings gear.
4. Select About.
5. Copy the full version number and note the environment URL.

Microsoft’s Dynamics 365 release notes use this same gear > About route when telling administrators how to confirm whether an update reached an organization.

Do not rely on a number copied from another environment. If an issue appears in production but not in a Dynamics 365 sandbox, compare the About values in both environments before investigating custom code or configuration.

How do you check the version in Finance or Supply Chain Management?

In Dynamics 365 Finance, Supply Chain Management, Commerce, or another finance and operations app, open Settings and select About. Record every version field shown, especially the application or product version and the platform version. Those values identify different layers of the deployed service.

1. Open the affected finance and operations environment.
2. Select the Settings icon in the navigation bar.
3. Select About.
4. Copy the application or product version.
5. Copy the platform version and any build value displayed beside it.

Keep the labels with the numbers when you paste them into a ticket. A platform build should not be reported as the application release. Microsoft’s official finance and operations service-update schedule lists application and platform versions separately, which is why both values matter when matching an environment to a serviced release.

How do you check the version in Business Central?

In Business Central, open Help & Support and find the version in the Troubleshooting section. You can open the page from the Help menu or search for “Help & Support” with the in-product search. Copy the complete version shown for the current environment.

1. Sign in to the Business Central company where the issue occurs.
2. Open the Help menu.
3. Select Help & Support.
4. Find the version under Troubleshooting.
5. Copy the version together with the environment and company names.

Microsoft documents that the Business Central Help and Support page shows the environment’s version. The same page also contains technical details that can help an administrator or partner investigate a support request.

What version details should you copy?

Copy the full version and build exactly as displayed, plus the app and environment names. The complete value is more useful than a shortened label because Microsoft release documentation maps serviced updates to specific builds. A reliable support note includes the following fields:

• Dynamics 365 application name
• Environment name and type, such as production or sandbox
• Environment URL
• Full version or build number
• Application and platform values, when the product shows both
• Date and time you checked
• Screenshot of the About or Help & Support page, with tenant-sensitive details redacted

Avoid translating the number into a release name from memory. Paste the original value first, then compare it with the appropriate Microsoft release page.

Is the version number the same as a release wave?

No. The version or build identifies the code deployed to an environment; a release wave groups planned features into a Microsoft delivery period. Two environments associated with the same wave can still show different build numbers while service updates move through regions and maintenance windows.

For Dataverse-based apps, Microsoft publishes platform builds through its general availability deployment schedule. Finance and operations apps have a separate service-update schedule. Business Central publishes product-specific update information. Match the number to the documentation for your product rather than comparing unrelated version schemes.

What should you do if two environments show different versions?

Treat different versions as a useful diagnostic clue, not proof of the root cause. Confirm that you opened the intended environments, capture both complete build values, and review the applicable Microsoft rollout information. Then test the failing process in the sandbox before changing production.

A sensible comparison is:

1. Confirm the environment names and URLs.
2. Capture both versions using the same in-app path.
3. Compare installed solutions, extensions, and feature settings.
4. Reproduce the issue with the same user role and data conditions.
5. Review recent deployment and service-update history.

Before a planned upgrade or risky configuration change, verify the Dynamics 365 backup and recovery options that apply to your environment. A version check identifies the deployed build; it does not replace an upgrade assessment, regression test, or recovery plan.

When should you involve a Dynamics 365 partner?

Bring in a Dynamics 365 partner when the version mismatch affects a business-critical process, a supported build still fails, or custom solutions complicate the diagnosis. Share the full version evidence first. That gives the consultant a concrete starting point for release-note review and reproducible testing.

Our Dynamics 365 services cover environment assessment, update planning, troubleshooting, and controlled deployment across CRM, ERP, and Power Platform workloads.

Frequently asked questions

These answers clarify the version terms that most often cause confusion during support and update planning.

Is a Dynamics 365 version number the same as a release wave?

No. A release wave describes a delivery period for planned capabilities. The version or build identifies the code deployed to a specific environment.

Do all Dynamics 365 environments have the same version?

Not necessarily. Production and sandbox can show different builds while an update is being tested or rolled out. Check the exact environment where the issue occurs.

Can a regular user check the Dynamics 365 version?

Users can usually open the in-app About or Help & Support page. If the option is unavailable, ask a Dynamics 365 administrator to retrieve the value from the affected environment.

Which part of the version number should I send to support?

Send the complete value, not only the major release. For Finance and Supply Chain Management, include both the application and platform values when they are shown.