Let me provide a comprehensive solution covering all three technical areas:
Browser Compatibility Configuration:
The primary issue is that modern browsers (Chrome 115+, Edge 115+, Firefox 120+) have enhanced third-party cookie restrictions that break Power BI embedded authentication. Here’s how to resolve this across your organization:
For Chrome/Edge Enterprise Deployment:
-
Create a Group Policy Object (GPO) or Intune policy with these settings:
- Policy: “Sites that can set cookies”
- Add these URLs:
-
For Chrome specifically, configure the JSON policy:
{
"CookiesAllowedForUrls": [
"[*.]powerbi.com",
"[*.]analysis.windows.net",
"[*.]pbidedicated.windows.net",
"[*.]dynamics.com",
"[*.]microsoftonline.com"
],
"ThirdPartyStoragePartitioningBlockedForOrigins": [
"https://[*.]powerbi.com",
"https://[*.]dynamics.com"
]
}
- Deploy via Chrome’s CloudManagement (for cloud-managed devices) or through registry keys:
- Path: HKLM\SOFTWARE\Policies\Google\Chrome
- Key: CookiesAllowedForUrls
- Type: REG_MULTI_SZ
- Values: (list the URLs above)
For Edge specifically:
- Use the same registry path but under: HKLM\SOFTWARE\Policies\Microsoft\Edge
- Edge inherits Chrome’s policy structure but has its own registry location
Third-Party Cookies Technical Details:
Power BI embedded uses an iframe to load visuals from the Power BI service. This cross-origin scenario requires third-party cookies for:
- Azure AD authentication tokens
- Power BI session state
- Report rendering context
- Embedded analytics telemetry
When browsers block these cookies, the authentication flow fails silently, resulting in empty frames.
Testing Cookie Configuration:
- Open browser DevTools (F12) → Application tab → Cookies
- Navigate to the capacity planning workspace
- Check for cookies from powerbi.com and analysis.windows.net domains
- If cookies are present but marked as “blocked”, your policy isn’t applied yet
- If no cookies appear at all, check browser policy application:
- Chrome: Navigate to chrome://policy and verify your policy appears
- Edge: Navigate to edge://policy
Power BI Embedded Configuration Validation:
After addressing browser settings, verify the D365 configuration:
-
System Parameters Check:
- Navigate: System administration → Setup → System parameters → Help tab
- Verify “Enable Power BI integration” is checked
- Confirm the Power BI workspace ID is correct
- Test the connection using “Test Power BI configuration” button
-
Capacity Planning Workspace Configuration:
- Navigate: Master planning → Setup → Capacity planning → Parameters
- Verify the “Enable embedded analytics” option is enabled
- Check that the report ID matches the published report in your Power BI workspace
- Confirm the workspace is assigned to a Power BI Premium capacity or embedded capacity (F64 or higher recommended)
-
Power BI Service Verification:
- Log into app.powerbi.com
- Navigate to the workspace specified in D365 parameters
- Verify the capacity planning reports are published and not in error state
- Check the workspace settings → Azure connections to ensure the D365 connection is active
- Verify the service principal or user account used by D365 has at least Member role in the workspace
-
Embedded Configuration:
- In Power BI workspace, go to Settings → Embed codes
- Verify the capacity planning reports are listed as embedded
- Check that “Embed for your organization” is enabled (not “Embed for your customers”)
Network and Proxy Considerations:
If browser policies are correctly applied but visuals still don’t render:
-
Check for SSL inspection or proxy interference:
- Power BI embedded requires direct HTTPS connections
- If your organization uses SSL inspection, add *.powerbi.com to the bypass list
- Verify WebSocket connections aren’t blocked (required for real-time updates)
-
Firewall rules - ensure these outbound connections are allowed:
-
Test from outside your corporate network (mobile hotspot) to isolate network-level blocking
Post-Upgrade Specific Issues:
Since this started after upgrading to 10.0.43:
-
Clear the browser cache and D365 application cache:
- Users should clear cookies specifically from *.dynamics.com and *.powerbi.com
- In D365, run: System administration → Inquiries → Batch jobs → Find and run “Clear cache” job
-
Verify the Power BI integration didn’t get disabled during upgrade:
- Check feature management for any new Power BI-related features that need enabling
- Review the upgrade log for any errors related to Power BI configuration
-
Re-publish the capacity planning reports from Power BI Desktop if the embedded report IDs changed during upgrade
Implement the browser policy changes first (can be done within hours via GPO), then validate the D365 and Power BI configurations. This should resolve the rendering issues for all users.
This draft is based on general Microsoft Dynamics 365 knowledge. It has not been verified against your specific version and environment. Practitioners: verify the steps and share your experience below.