Consent Pop-Up Doesn’t Appear
Cause: Browser pop-up blocker is preventing the consent window from opening.
Fix:
- Check your browser’s address bar for a blocked pop-up notification
- Allow pop-ups for
portal.contraforce.com
- Retry the consent step
In Chrome: click the pop-up blocked icon in the address bar → “Always allow pop-ups from portal.contraforce.com” → retry.
Consent Fails with Permissions Error
Cause: The account used for consent doesn’t have Global Administrator or Security Administrator role in Entra ID.
Fix:
- Verify the account has Global Administrator role in Microsoft Entra ID
- Go to Entra ID → Roles and administrators to check
- If needed, have an existing Global Admin assign the role
- Retry the consent flow with the correct account
Azure Deployment Fails
Cause: The account used doesn’t have Subscription Owner access, or Azure Policy restrictions are blocking resource creation.
Fix:
- Verify Subscription Owner role in the target Azure subscription
- Check for Azure Policies that restrict resource types or regions
- Ensure the subscription has sufficient quota for the resources being deployed
- If policies are blocking deployment, work with your Azure admin to create an exception
Lighthouse Delegation Failed
Cause: Existing Azure Lighthouse delegation is already present, or an Azure Policy restriction is preventing delegation.
Fix:
- Check for existing Lighthouse delegations in the target subscription
- Remove any existing ContraForce delegations
- Check for restrictive Azure Policies
- Retry the delegation
Cause: One or more consent steps were skipped or failed silently.
Fix:
- Go to Settings → Workspace Settings → Module Configuration
- Check which consent steps show as incomplete
- Click the incomplete step to re-run the consent flow
- Use Global Admin credentials and ensure pop-ups are allowed
Still Stuck?
Contact support@contraforce.com with your workspace name, the step where you’re stuck, and any error messages or screenshots.
