Listen to this Post
Introduction:
Microsoft Copilot Studio, a powerful AI-driven tool for building conversational agents, recently changed its licensing model—requiring a prepaid message pack before assigning user licenses. This shift has blocked many teams from experimenting with the platform. Here’s a verified workaround to grant access without upfront commitments.
Learning Objectives:
- Understand the new Copilot Studio licensing requirements.
- Learn how to assign access via Azure security groups.
- Explore pay-as-you-go billing as a flexible alternative.
You Should Know:
1. Assigning Access via Azure Security Groups
Instead of assigning individual licenses, Microsoft now allows admins to grant access via Azure security groups.
Steps:
1. Navigate to the Power Platform Admin Center.
- Under Tenant Settings, locate Copilot Studio author settings.
- Assign an Azure security group containing users who need access.
Why This Works:
This bypasses the need for direct license assignments, enabling teams to experiment freely.
2. Enabling Pay-As-You-Go Billing
Microsoft introduced a consumption-based model, ideal for pilot projects.
Steps:
1. Link an Azure subscription to Copilot Studio.
2. Configure pay-per-message billing in the Azure portal.
3. Monitor usage via Azure Cost Management.
Key Command (Azure CLI):
az billing subscription link --subscription-id <YOUR_SUB_ID> --cost-management
This ensures real-time tracking of message costs.
3. Verifying License Compliance
Ensure users aren’t accidentally consuming paid features without authorization.
PowerShell Command:
Get-MgUserLicenseDetail -UserId "[email protected]" | Where-Object { $_.SkuPartNumber -eq "COPILOT_STUDIO" }
This checks if a user has an active Copilot Studio license.
4. Auditing Copilot Studio Usage
Track who is accessing the platform and their activity.
Microsoft 365 Compliance Command:
Search-UnifiedAuditLog -RecordType "PowerPlatformCopilotStudio" -StartDate (Get-Date).AddDays(-30) -EndDate (Get-Date)
This retrieves a 30-day log of Copilot Studio actions.
5. Restricting Access to Approved Users
Prevent unauthorized usage by enforcing conditional access.
Azure AD Conditional Access Policy (CLI):
az ad policy create --display-name "Restrict Copilot Studio Access" --rules @restrict-copilot.json
Sample JSON rule:
{
"applications": {
"includeApplications": ["00000000-0000-0000-0000-000000000000"] // Copilot Studio App ID
},
"users": {
"includeGroups": ["<SECURITY_GROUP_ID>"]
}
}
What Undercode Say:
- Key Takeaway 1: Microsoft is pushing organizations toward committed billing models, but workarounds exist for flexibility.
- Key Takeaway 2: Azure security groups and pay-as-you-go billing provide scalable, low-risk entry points for AI adoption.
Analysis:
The licensing shift reflects Microsoft’s strategy to monetize AI tools more aggressively. However, the Azure integration workaround ensures enterprises can still innovate without lock-in. Expect further policy refinements as adoption grows.
Prediction:
Future updates may enforce stricter license checks, but Azure-based access will likely remain a loophole for agile teams. Organizations should automate compliance checks to avoid unexpected costs.
For official documentation, refer to:
IT/Security Reporter URL:
Reported By: Samuelboulanger Copilotstudio – Hackers Feeds
Extra Hub: Undercode MoN
Basic Verification: Pass ✅
