Verification & Testing: Control 2.15 - Environment Routing and Auto-Provisioning
Last Updated: January 2026
Manual Verification Steps
Test 1: Verify Environment Group Configuration
- Sign in to Power Platform Admin Center
- Navigate to Environments > Environment groups
- Open each group and verify membership
- EXPECTED: Groups contain correct environments per governance design
Test 2: Verify Routing Rules
- In each environment group, select Rules
- Review each rule's conditions and target
- Verify rule priorities are correct
- EXPECTED: Rules target appropriate environments with correct conditions
Test 3: Test Routing - Security Group Rule
- Sign in as a user in a security group with a routing rule
- Navigate to Power Apps
- Click + Create to start a new app
- Check which environment is selected by default
- EXPECTED: User is routed to environment specified in rule
Test 4: Test Routing - No Rule Match
- Sign in as a user NOT matching any routing rules
- Navigate to Power Apps or Copilot Studio
- Check which environment is selected by default
- EXPECTED: User is routed to default/fallback environment
Test 5: Verify Routing Documentation
- Review routing rule documentation
- Compare documented rules to configured rules
- EXPECTED: Documentation matches actual configuration
Test Cases
| Test ID | Scenario | Expected Result | Pass/Fail |
|---|---|---|---|
| TC-2.15-01 | Environment groups contain correct environments | Membership correct | |
| TC-2.15-02 | Security group rule routes correctly | User sees target env | |
| TC-2.15-03 | Domain rule routes correctly | User sees target env | |
| TC-2.15-04 | Rule priority respected | Higher priority wins | |
| TC-2.15-05 | No-match user gets default env | Default env selected | |
| TC-2.15-06 | Documentation matches config | All rules documented | |
| TC-2.15-07 | Rule change requires approval (Zone 3) | Change blocked without approval |
Evidence Collection Checklist
Environment Group Configuration
- Screenshot: PPAC > Environment groups list
- Screenshot: Each group's environment membership
- Screenshot: Each group's routing rules
- Export: Environment configuration JSON
Routing Rules
- Screenshot: Routing rules with conditions and priorities
- Document: Rule-to-target mapping table
- Screenshot: Default environment configuration
Testing Evidence
- Screenshot: Test user routed to correct environment
- Screenshot: No-match user routed to default
- Document: Test case results table
Evidence Artifact Naming Convention
Control-2.15_[ArtifactType]_[YYYYMMDD].[ext]
Examples:
- Control-2.15_EnvGroups_20260115.png
- Control-2.15_RoutingRules_20260115.png
- Control-2.15_TestResults_20260115.xlsx
- Control-2.15_EnvConfig_20260115.json
Attestation Statement Template
## Control 2.15 Attestation - Environment Routing
**Organization:** [Organization Name]
**Control Owner:** [Name/Role]
**Date:** [Date]
I attest that:
1. Environment groups are configured per governance design
2. Routing rules direct users to appropriate environments
3. Rule priorities are correctly ordered
4. Default environment fallback is appropriately governed
5. Routing changes follow change control process
6. Configuration documentation is current and accurate
**Environment Groups Configured:** [Number]
**Routing Rules Active:** [Number]
**Signature:** _______________________
**Date:** _______________________
Back to Control 2.15 | Portal Walkthrough | PowerShell Setup | Troubleshooting