Azure DevOps Pipelines

All deployments to DfE's Dynamics 365 environments should be performed using automated Azure DevOps pipelines. This includes the deployment of Dynamics 365 solutions, Power Pages portals and associated reference data. Manual deployments are avoided to ensure consistency, repeatability and control across all environments.

Application source code, configuration and deployment assets must be stored in Azure DevOps repositories.

Why Azure DevOps

Azure DevOps gives an integrated platform for source control, build and release management, and auditing. Using Azure DevOps pipelines aligns with Microsoft best practice for Dynamics 365 DevOps.

Azure DevOps provides:

  • Automated and repeatable deployments
  • Clear audit trails and deployment history
  • Reduced deployment risk caused by manual changes
  • Consistent promotion across environments
  • Integrates natively with Microsoft Power Platform and Azure

Azure DevOps pipelines are used to deploy the following components:

  • Dynamics 365 managed and unmanaged solutions
  • Power Pages (portal) configuration and content
  • Reference and configuration data required by solutions

Source Control Standard

All Dynamics 365 solution source, portal configuration and deployment scripts must be stored in Azure DevOps repositories. This ensures:

  • Version control of all changes
  • Clear history of who changed what and when
  • Ability to review and approve changes before deployment
  • Consistency between environments

Configuration and reference data required for deployments should be defined and included in source control alongside solution assets.

Best Practice Guidelines

The following best practices apply to Dynamics 365 deployments:

  • All deployments must be executed via Azure DevOps pipelines
  • No manual solution imports to test or production environments
  • Source repositories must be hosted in Azure DevOps
  • Pipelines should be parameterised to support multiple environments
  • Reference data deployments should be automated and repeatable
  • Production deployments should be controlled and auditable

What This Standard Avoids

This standard deliberately avoids:

  • Manual deployments and ad hoc environment changes
  • Untracked solution changes made directly in target environments
  • Source code stored outside of Azure DevOps
  • Inconsistent deployment approaches across teams or services

Standardised Pipeline Approach

An SDT standardised approach to Azure DevOps pipelines for Dynamics 365 deployments is available and must be used wherever possible. This approach provides a consistent, reusable pipeline structure for deploying Dynamics solutions, Power Pages (portals) and reference data across environments, along with AI generated release notes.

The standard pipelines are designed to promote best practice, reduce duplication and ensure deployments are secure, auditable and repeatable.

Documentation, guidance and example pipeline templates are maintained on the Azure DevOps wiki. Teams should refer to the DevOps wiki for the latest standards, usage guidance and implementation details before creating or modifying deployment pipelines.