Portal Walkthrough: Control 1.18 - Application-Level Authorization and RBAC
Last Updated: January 2026 Portal: Power Platform Admin Center, Microsoft Entra Admin Center Estimated Time: 3-5 hours
Prerequisites
- Power Platform Admin role
- Entra Global Admin or Privileged Role Admin
- Dataverse System Admin for security role creation
Step-by-Step Configuration
Step 1: Create Security Groups
- Open Microsoft Entra Admin Center
- Navigate to Groups > All groups
- Create security groups:
SG-PowerPlatform-Admins-ProdSG-CopilotStudio-Makers-ProdSG-CopilotStudio-Viewers-ProdSG-CopilotStudio-Testers-Prod
Step 2: Create Custom Dataverse Security Roles
- Open Power Platform Admin Center
- Select environment > Settings > Users + permissions > Security roles
- Create custom roles:
FSI - Agent Publisher: - Bot: Create, Read, Write, Delete, Append, Append To - Bot Component: Create, Read, Write, Delete - Environment: Read
FSI - Agent Viewer: - Bot: Read - Bot Component: Read - Environment: Read
FSI - Agent Tester: - Bot: Read, Write - Bot Component: Read - Environment: Read
Step 3: Assign Roles to Security Groups
- In Power Platform Admin Center
- Select environment > Settings > Users + permissions > Teams
- Create teams linked to security groups
- Assign security roles to teams
Step 4: Configure Privileged Identity Management
- Open Microsoft Entra Admin Center
- Navigate to Identity governance > Privileged Identity Management
- Select Microsoft Entra roles > Roles
- Configure PIM for Power Platform Admin:
- Maximum activation duration: 4 hours
- Require approval: Yes (CISO/Security Lead)
- Require MFA on activation: Yes
Step 5: Configure Column-Level Security
- In Power Platform Admin Center > Environment > Settings
- Navigate to Data management > Field security profiles
- Create profile:
FSI-SensitiveFields - Add sensitive columns (SSN, Account Balance, Credit Score)
- Assign allowed roles/users
Step 6: Set Up Access Reviews
- Open Microsoft Entra Admin Center
- Navigate to Identity governance > Access reviews
- Create review for each security group:
- Frequency: Quarterly (Zone 2/3), Annual (Zone 1)
- Reviewers: Group owners
- Auto-remove on non-response: Yes
Configuration by Governance Level
| Setting | Baseline (Zone 1) | Recommended (Zone 2) | Regulated (Zone 3) |
|---|---|---|---|
| Role Assignment | Standard roles | Group-based custom | Least-privilege custom |
| Access Review | Annual | Semi-annual | Quarterly |
| PIM | Not required | Admin roles | All privileged roles |
| Approval | Self-service | Manager | Multi-level |
| Column Security | None | Sensitive fields | All PII/NPI fields |
Step 7: Configure Agent Action Consent
- Open Copilot Studio (https://copilotstudio.microsoft.com)
- Navigate to Agents and select each agent
- Go to Actions and locate each configured action
- For every action, enable "Ask the user before running this action"
- Where available, set "How do you want to ask the user?" to "You create the message" and configure a clear, human-written description of what the action will do
- Repeat for all agents in Zone 2 and Zone 3 environments
Step 8: Configure Connected Agent Governance
- In Copilot Studio, select each agent
- Navigate to Settings > under Connected Agents (Preview)
- Locate the toggle "Let other agents connect to and use this one"
- Set to Disabled by default
- Enable only with:
- Documented business justification
- Cross-agent data handling review
- Compliance officer sign-off
- Document all approved inter-agent connections and review quarterly
Step 9: Review Environment Admin Roles
- Sign in to Power Platform Admin Center (https://admin.powerplatform.microsoft.com)
- Navigate to Environments > select the target environment > Settings > Users + Permissions > Users
- Review all users with System Administrator role
- For any assignment that is not justified, select the user > Manage Roles > remove System Administrator
- Ensure fewer than 10 administrators per environment
- Document all admin role assignments with business justification
Validation
After completing these steps, verify:
- Security groups created and populated
- Custom security roles assigned to groups
- PIM configured for admin roles
- Access reviews scheduled
- Column-level security enforced
- All agent actions have "Ask the user before running this action" enabled (Copilot Studio > Agent > Actions)
- Connected agent access disabled for all agents unless explicitly approved (Copilot Studio > Agent > Settings > Connected Agents)
- Admin count is below 10 per environment (PPAC > Environment > Users + Permissions)
Back to Control 1.18 | PowerShell Setup | Verification Testing | Troubleshooting
Updated: February 2026 | Version: v1.2 | Classification: Portal Walkthrough