MOP Release Management

Manage vendor MOP releases and sequential execution across Azure organizations

Create New Release

Format: R{major}.{minor}.{patch}.{build}
Directory containing vendor J2 templates

Execution Order

MOPs will be executed sequentially in this order:

  1. EUS2
    East US 2 (Primary)
  2. WUS2
    West US 2 (Primary West)
  3. WUS3
    West US 3 (Modern)
  4. SCUS
    South Central US (Hub)
  5. EUS2LEA
    East US 2 LEA (Early Access)
  6. WUS2LEA
    West US 2 LEA (Early Access)
Only one organization executes at a time

Existing Releases

Version Description MOPs Status Created Actions
R11.5.3.3 Example release with vendor MOPs 25 MOPs Pending 2025-08-02
system
R11.5.3.6 Final release validation with all 25 vendor MOPs and 6 regional variable files 25 MOPs Pending 2025-08-01
validation_test
R11.5.3.5 Test release with regional variable files - 25 vendor MOPs with unique Azure organization configs 25 MOPs Pending 2025-08-01
regional_test
R11.5.3.4 Major Q1 2025 Release: Complete infrastructure automation with 25 vendor MOPs covering all operational aspects 25 MOPs Pending 2025-08-01
vendor_team