Skip to content

Prerequisites

Requirements for deploying the DR Testing Framework solution.

PowerShell Requirements

Requirement Version Purpose
PowerShell 7.1+ Core runtime (#Requires -Version 7.1) — uses Get-Date -AsUTC added in 7.1
Pester 5.0+ Test execution (for running Invoke-DRTest.Tests.ps1 and Export-DREvidence.Tests.ps1)

Installation

# Install Pester (if not already present)
Install-Module -Name Pester -MinimumVersion 5.0 -Force -Scope CurrentUser

Entra ID App Registration

For non-interactive (automated) execution, register a service principal:

  1. Register an application in Microsoft Entra ID → App registrations
  2. Create a client secret (or certificate) and record the expiry date
  3. Note the following values from the app registration overview:
  4. Directory (tenant) ID
  5. Application (client) ID
  6. Client secret value

Environment Variables

Set these environment variables before running the scripts:

Variable Description
AZURE_TENANT_ID Entra ID directory (tenant) ID
AZURE_CLIENT_ID App registration application (client) ID
AZURE_CLIENT_SECRET Client secret value 
$env:AZURE_TENANT_ID     = "<your-tenant-id>"
$env:AZURE_CLIENT_ID     = "<your-client-id>"
$env:AZURE_CLIENT_SECRET  = "<your-client-secret>"

Security note: Store secrets in a key vault or CI/CD secret store for production use. Avoid persisting credentials in shell profiles or scripts.

Permissions

Power Platform & Dataverse

The executing identity (user or service principal) requires the following roles:

Role Environment Purpose
Power Platform Admin Tenant-level Performing PPAC environment restore operations (out of scope of this script — listed for the operator)
System Administrator (or equivalent) Dataverse environment Write validation results to fsi_drtestresult table

For service principal access, add the app as an application user in each target Dataverse environment and assign the appropriate security roles.

Dataverse Schema

The fsi_drtestresult table must exist in the target Dataverse environment before running DR tests. Create it using one of:

  • Manual creation — Follow the column definitions in dataverse-schema.md
  • Schema script — Run create_drt_dataverse_schema.py (when available) with --output-docs to generate schema documentation

Note: A deployable Power Platform solution package for automated schema deployment is planned. Until then, create the table manually as described in the README.

Network Requirements

The scripts communicate with Microsoft cloud endpoints. Verify that firewall and proxy rules permit outbound HTTPS traffic to the following:

Endpoint Protocol Purpose
*.crm.dynamics.com HTTPS Dataverse API (commercial cloud)
*.microsoftdynamics.us HTTPS Dataverse API (GCC High)
*.appsplatform.us HTTPS Dataverse API (GCC High alternate)
*.dynamics.cn HTTPS Dataverse API (China sovereign cloud)
login.microsoftonline.com HTTPS Entra ID token acquisition (commercial)
login.microsoftonline.us HTTPS Entra ID token acquisition (GCC High)
login.chinacloudapi.cn HTTPS Entra ID token acquisition (China)

Only the endpoints matching your cloud environment are required. Most organizations need only the commercial (*.crm.dynamics.com and login.microsoftonline.com) endpoints.

Dependencies

Solution Version Purpose
Environment Lifecycle Management v1.2.0+ Environment context (informational — not imported or validated at runtime)

Python Requirements (Schema Script)

If using the Dataverse schema creation script:

Requirement Version Purpose
Python 3.9+ Schema script runtime
msal Latest Dataverse authentication via MSAL 
pip install msal

Licensing

Requirement Purpose
Power Platform per-app or per-user license Required for any Power Platform environment hosting the agents under validation
Dataverse capacity Storage for fsi_drtestresult validation records

Power Platform environment backups are managed by Microsoft and are not administered through Azure Backup. Environment restore is performed via the Power Platform admin center (PPAC) restore APIs, not by this framework.

Caveat: This solution aids in meeting operational resilience expectations such as FFIEC BCP, OCC Heightened Standards, FINRA Rule 4370, and SEC Rule 17a-4(f). It does not by itself satisfy any single regulation. (Note: OCC Bulletin 2011-12 governs model risk, not business continuity — DR aligns to OCC Heightened Standards instead.) Organizations should verify that their DR testing scope, frequency, and evidence retention meet their specific regulatory obligations.