Some pilot users in Microsoft 365 Copilot programs report that the Business Chat feature, accessed via copilot.microsoft.com or the Teams app, shows a blank screen or a permissions error. This issue typically occurs because the pilot tenant lacks the correct service plan assignment or because a conditional access policy blocks the chat endpoint. This article explains the root cause and provides three tested fixes to restore Business Chat access for pilot users.
Key Takeaways: Restoring Business Chat for Copilot Pilot Users
- Microsoft 365 admin center > Billing > Licenses > Copilot for Microsoft 365: Verify the pilot user has the service plan enabled for Business Chat.
- Azure AD > Conditional Access > Policies: Exclude the Business Chat app ID 6a8b00e8-1a5a-4fd4-bf8e-5b4f1b2c9d3e from any blocking policy.
- Microsoft 365 admin center > Health > Service Health: Check for an active advisory on Business Chat throttling or outage affecting pilot tenants.
Why Pilot Users Lose Access to Business Chat
Business Chat, also called BizChat, is a Copilot feature that lets users query Microsoft Graph data across documents, emails, and meetings. For pilot users, access depends on two technical components: the service plan assignment in the Microsoft 365 license and the Azure AD application registration for the chat web app.
The most common root cause is a missing or disabled service plan. The Copilot for Microsoft 365 license includes several service plans, but the Business Chat plan can be toggled off by an administrator during license assignment. When the plan is off, the user sees a blank page or an error message stating that Copilot is not available.
A second cause involves conditional access policies. Many organizations block personal device access or require multi-factor authentication for web apps. If the policy targets the Business Chat application ID but does not include an exception for pilot users, the authentication request is denied and the chat fails to load.
A third cause is a service-side throttle or outage. Microsoft occasionally limits Business Chat access during pilot phases to manage load, and this appears as a grayed-out chat window or a loading spinner that never resolves.
Steps to Restore Business Chat Access for Pilot Users
Follow these steps in order. Each step addresses one of the root causes described above.
- Verify the Business Chat service plan is enabled
Open the Microsoft 365 admin center. Go to Billing > Licenses. Select the Copilot for Microsoft 365 license. Under the Assigned licenses tab, locate the pilot user. Click the user name. In the pane that opens, expand Apps. Scroll to Microsoft Copilot for Microsoft 365 and confirm the toggle next to Business Chat is set to On. If it is Off, toggle it On and click Save. - Check conditional access policies for the Business Chat app
Open the Azure AD admin center at entra.microsoft.com. Go to Protection > Conditional Access > Policies. Review each policy that targets Cloud apps. Click a policy and check if Microsoft Copilot for Microsoft 365 or the app ID 6a8b00e8-1a5a-4fd4-bf8e-5b4f1b2c9d3e is included. If a policy blocks access, create an exclusion for the pilot user group. Under Assignments > Users and groups, select Exclude and add the pilot group. Save the policy. - Verify service health for Business Chat
In the Microsoft 365 admin center, go to Health > Service Health. Look for an advisory titled Microsoft Copilot for Microsoft 365 or Business Chat. If the status shows Service degradation or Advisory, click the entry. Review the message for a timeline. If Microsoft reports a known issue, wait for the resolution. No admin action is required for service-side throttling. - Force a license refresh on the user account
If the service plan is enabled but the user still cannot access Business Chat, force a license refresh. In the Microsoft 365 admin center, go to Users > Active users. Select the pilot user. Click Licenses and apps. Uncheck the Copilot for Microsoft 365 license, click Save changes, then recheck the license and click Save changes again. The user must sign out of all Microsoft 365 apps and sign in again. - Clear browser cache for the chat domain
Stale cookies or cached scripts can cause a blank Business Chat page. Open the browser settings. Clear cached images and files for the domain copilot.microsoft.com and all subdomains. On Chrome, go to Settings > Privacy and security > Clear browsing data. Select Cached images and files. Set the time range to All time. Click Clear data. Reload the Business Chat page.
If Business Chat Still Has Issues After the Main Fix
Business Chat returns a 403 Forbidden error
A 403 error typically means the user lacks the required license or the tenant has a service-level block. Verify the user has a Copilot for Microsoft 365 license assigned and that the tenant is enrolled in the pilot program. Contact Microsoft support and request a tenant health check for the Business Chat service.
Business Chat loads but shows no data
This symptom occurs when the user is signed in with a personal Microsoft account instead of a work or school account. Sign out of all Microsoft accounts. Open an InPrivate or Incognito window. Sign in at copilot.microsoft.com using the work account that has the Copilot license. If the issue persists, check that the user has a valid Exchange Online mailbox and a SharePoint license, because Business Chat requires these for data retrieval.
Business Chat is grayed out in the Teams app
The Teams app may cache an older version of the Copilot interface. Clear the Teams cache by closing Teams, deleting the folder %appdata%\Microsoft\Teams, and restarting Teams. If the chat is still grayed out, update Teams to the latest version by clicking the three-dot menu in the title bar and selecting Check for updates.
Copilot for Microsoft 365 License vs Business Chat Service Plan: Key Differences
| Item | Copilot for Microsoft 365 License | Business Chat Service Plan |
|---|---|---|
| Description | Entitlement to use Copilot across all Microsoft 365 apps | Sub-feature that enables the chat interface and Graph queries |
| Admin control | Assigned per user in Billing > Licenses | Toggled per user in the license assignment pane under Apps |
| Impact if disabled | User cannot open Copilot in any app | User can open Copilot in Word or Excel but not Business Chat |
| Conditional access target | App ID not used for licensing | App ID 6a8b00e8-1a5a-4fd4-bf8e-5b4f1b2c9d3e controls web access |
Pilot users who cannot access Business Chat can resolve the issue by enabling the service plan, adjusting conditional access policies, and clearing browser cache. If the problem is service-side, wait for the advisory to close. For persistent access failures, verify the user account type and license assignment in the Microsoft 365 admin center. As an advanced step, use the Microsoft 365 network connectivity test at connectivity.microsoft.com to confirm that the Business Chat endpoint copilot.microsoft.com is reachable from the user network.