Microsoft Dynamics 365 On-Premises Upgrade Guide (v8.1/8.2 to 9.1)

🚀 Microsoft Dynamics 365 On-Premises Upgrade Guide (v8.1/8.2 to 9.1)

Upgrading Microsoft Dynamics 365 On-Premises from version 8.1 or 8.2 to 9.1 is a significant milestone for organizations aiming to modernize their CRM infrastructure. This guide is written from the perspective of an engineer who has led these upgrades, sharing field-tested steps, lessons learned, and best practices.

📎 SOP Reference

For full technical documentation, screenshots, and command-line examples, please refer to my published SOP document:
🔗 https://docs.google.com/document/d/e/2PACX-1vRrm-d9dCsGxoXgHGnic2AZDfJUVVog62SXgqcXHx1faPI0sgb819L6CHQh6ItZR4Q4MM-9QLojiw_6/pub

🔍 Why Upgrade to 9.1?

Dynamics 365 9.1 offers substantial enhancements in performance, compliance, and security. The earlier versions (8.1/8.2) no longer receive regular cumulative updates and may not support the latest OS or SQL versions.

🧰 Pre-Upgrade Engineering Tips

·         - Take full backups of databases and encryption keys.

·         - Validate available disk and memory resources.

·         - Create VM snapshots before starting upgrades.

·         - Prepare all necessary pre-requisite installers.

TIP 💡: Always test the upgrade process in a sandbox environment using a restored backup.

🧭 Recommended Microsoft Upgrade Flow

Based on Microsoft documentation and upgrade experience:

1. Ensure current environment is upgraded to Dynamics 365 v8.2.

2. Apply the latest CU for v8.2 (if not done already).

3. Set up a new environment with Windows Server 2019/2022 and SQL Server 2019.

4. Install Dynamics 365 9.0 from official Microsoft installer.

5. Apply latest CU for version 9.0 (e.g., CU 50).

6. Install Dynamics 365 9.1 base version (minimum 9.1.1.914).

7. Apply latest CU for 9.1 (e.g., CU 38 – 9.1.38.10).

8. Use Deployment Manager to import and upgrade Org DB.

9. Reconfigure SSRS Report Extensions.

10. Revalidate workflows, plugins, and reports.

🔐 IFD and Claims Configuration (Optional)

If you're exposing your CRM to external users, configure ADFS and IFD post-upgrade.
- Use proper SSL certificates.
- Configure relying party trust in ADFS.
- Test `/adfs/ls/` and federation metadata URLs.
Microsoft guide: https://learn.microsoft.com/en-us/dynamics365/customerengagement/on-premises/deploy/configure-the-ad-fs-server-for-ifd

🧪 Post-Upgrade Validation

·         - Confirm CRM service health (via logs & Event Viewer).

·         - Test custom reports and dashboards.

·         - Verify Outlook and external app integrations.

·         - Create rollback plan before going live.

📦 CU Versions Reference

• 9.0.50.03 – Oct 2023

• 9.1.38.10 – July 2025

📘 Full CU List: https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-on-premises-cumulative-updates

📚 Microsoft Resources

• Upgrade Guide: https://learn.microsoft.com/en-us/dynamics365/customerengagement/on-premises/deploy/update-to-v91

• CU List: https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-on-premises-cumulative-updates

• Claims & IFD: https://learn.microsoft.com/en-us/dynamics365/customerengagement/on-premises/deploy/configure-the-dynamics-365-server-for-claims-based-authentication

🧠 Final Thoughts

Upgrades require careful planning, time allocation, and testing. Do not rush this process. My recommendation is to always isolate the upgrade steps in a test environment and track each action in a log file. By following Microsoft’s structured process—and supplementing it with field-tested insights—you can upgrade with confidence.