Copilot Chat Turned Off by Your Organisation? How Admins Fix It

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for Copilot Chat Turned Off by Your Organisation? How Admins Fix It.
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for Copilot Chat Turned Off by Your Organisation? How Admins Fix It.

An admin switches Copilot Chat back on by unblocking the Copilot app in the Microsoft 365 admin center: Settings, Integrated apps, Blocked apps, select Copilot, Unblock app. That block is what produces "Copilot Chat was turned off for your organization". Then confirm pinning, Edge settings and network allow-lists, and test with a staff account.

The Complete Excel Course with AI Integration

From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.

By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner

Buy now

The message is rarely a bug. Microsoft's own documentation says users blocked through Integrated Apps see exactly that experience, which means someone, at some point, blocked or restricted the Copilot app on purpose or by a side effect. The fix is to find which setting did it, change that one, and then check the three or four places that also affect whether Copilot Chat appears for people.

What does "Copilot Chat was turned off for your organization" mean?

The "Copilot Chat was turned off for your organization" message means the Copilot app is blocked for that user in the Integrated Apps portal of the Microsoft 365 admin center. Microsoft says blocking Copilot there is a tenant-wide control that can be scoped to users or groups, and its Manage Copilot Chat page says the block covers the Copilot app, Teams, Outlook and Copilot Chat on the web.

It helps to separate three situations that look alike to a member of staff.

What staff seeLikely causeWhere the admin looks
"Copilot Chat was turned off for your organization"Copilot app blocked in Integrated Apps (for everyone or for scoped users)Settings > Integrated apps > Blocked apps and Available apps
No Copilot icon in Teams or Outlook, but the web app worksPinning setting or Teams app policyCopilot > Settings > Pin Microsoft Copilot Chat; Teams admin center policies
Page will not load or loops back to sign-inFirewall, proxy, Conditional Access or personal-account sign-inAllow-lists for *.cloud.microsoft; sign-in account type
Copilot works but the Edge sidebar icon is missingEdge policyEdge group policy settings

Start with the first row. If staff literally see the blocked message, the remaining rows are secondary checks you make after the unblock. If Copilot Chat opens but staff are told that agents are disabled, that is controlled separately, under Agents > Settings in the admin center; our tutorial on switching Copilot agents back on as an admin covers that case.

How does an admin unblock Copilot Chat in the admin center?

An admin unblocks Copilot Chat from Settings, Integrated apps, Blocked apps: select the Copilot app, choose Unblock app, read the status it will revert to, and confirm. Microsoft says the app returns to the last saved availability and deployment state from before it was blocked.

  1. Sign in to the Microsoft 365 admin center as a Global Administrator. Microsoft's Integrated Apps page says its controls are available to Global Admins.
  2. Go to Settings, then Integrated apps.
  3. Open the Blocked Apps list and select the Copilot app. Microsoft notes the app appears as "CoPilot" and that its settings apply to both Microsoft Copilot and Copilot Chat.
  4. Select Unblock app.
  5. Read the availability and deployment status the app will revert to. This is the last saved state from before the block, or the default tenant setting if none was ever saved.
  6. Select Unblock. The app now moves to the Available Apps list, the Deployed Apps list, or both.

Take a screenshot of the state before and after. If the app reverts to "Specific users/group in the organization can install" with an old group, the problem is not fully solved, and the next section covers it.

Microsoft's two admin pages describe Teams differently. The Integrated Apps page says changes there affect only Outlook and the Microsoft Copilot app, and that Teams keeps the settings made in the Teams admin center; the Manage Copilot Chat page lists Teams among the places a Copilot block reaches. Check both: after the unblock, confirm in the Teams admin center that the Copilot app is allowed and pinned for the people who need it.

What if the app is not blocked but only some people can install it?

If Copilot sits in Available Apps with specific users or groups allowed, everyone outside that group is effectively locked out. Change the availability to all users, or add the missing group, from the app's overview pane under Edit Users.

This situation is common because Microsoft's own guidance for keeping Copilot Chat away from unlicensed users says to select "Specific users/group in the organization can install" and assign a group containing only licensed users. A previous admin may have followed that advice, or a rollout plan may have set it deliberately and then been forgotten. Microsoft says the app is then available only to that group, so everyone else loses Copilot Chat in the Copilot app and Outlook. Microsoft describes the "turned off" page for blocked users, so when someone reports it, check the Available Apps list as well as Blocked Apps: a forgotten block and a forgotten group often sit side by side.

  1. In Settings > Integrated apps, open the Available Apps list and select the Copilot app.
  2. Choose Edit Users (or the Users tab in the overview pane).
  3. Pick the availability: No users in the organization can install, All users in the organization can install, or Specific users/group in the organization can install.
  4. Select Save.

Microsoft's page adds one subtlety: the availability setting controls who may install and use the app themselves, and does not affect admin-deployed apps. If you want Copilot pre-installed rather than self-installed, deploy it from the same portal with Deploy app and choose the users.

A worked example: a 22-person signage company

An illustrative signage company has 22 staff and five Microsoft 365 Copilot licences held by the owner, two designers and two estimators. The other 17 staff, who work in production and installation, see "Copilot Chat was turned off for your organization". The owner wants all 22 to use free Copilot Chat for tasks like rewriting job-sheet notes.

  1. The admin opens Settings > Integrated apps > Blocked Apps and finds Copilot there. A past rollout had blocked it for a group named "Production and install" to keep Copilot Chat away from unlicensed staff.
  2. The admin selects the app, chooses Unblock app and reads the status it will revert to: "Specific users/group in the organization can install", assigned to a group named "Copilot licensed". The admin selects Unblock.
  3. In Available Apps, the admin opens Copilot, selects Edit Users, changes it to "All users in the organization can install", then Save. Without this step, the unblock would leave the 17 still outside the app.
  4. The admin opens Copilot > Settings > Pin Microsoft Copilot Chat and confirms "Pin Copilot Chat in Microsoft 365 apps (recommended)" is selected.
  5. In the Teams admin center, the admin checks the app permission policy so the Copilot app is allowed for everyone, and an app setup policy pins it.
  6. The admin tests with one installer's account (unlicensed) in a private browser window at copilot.cloud.microsoft, confirming the Work label and the green data-protection shield.
  7. The next morning the owner sends the staff message in the last section of this tutorial.

Total admin time in this illustration: about 25 minutes, plus the wait for pinning to apply. The point is the order: find the cause, fix it, test with a representative unlicensed account, and only then announce.

If you want help fitting Copilot Chat into how your business runs, I offer one-to-one AI consultations for small businesses.

Which admin role does each change need?

Integrated Apps changes need a Global Administrator according to Microsoft's Integrated Apps page, while the pinning setting needs the AI Administrator role. Microsoft recommends the role with the fewest permissions and reserving Global Administrator for cases where nothing narrower works.

TaskWhereRole Microsoft names
Unblock or scope the Copilot appSettings > Integrated appsGlobal Administrator
Pin or unpin Copilot Chat in Microsoft 365 appsCopilot > Settings > Pin Microsoft Copilot ChatAI Administrator
Pin the Copilot app on the Windows taskbarSame page, Windows taskbar linkIntune Administrator, for users with an active Intune licence
Teams app permission and setup policiesTeams admin centerA Teams admin role
Custom link on the blocked pageCopilot > Settings > View allAn admin account (Microsoft says "an administrator account")

In a very small business one person often holds every role. Even then, take the Global Administrator step, sign out, and do the rest with a narrower account if you have one.

How do you check pinning for Teams and Outlook?

Check Copilot Chat pinning in the admin center under Copilot > Settings > Pin Microsoft Copilot Chat, where "Pin Copilot Chat in Microsoft 365 apps (recommended)" is the default. Microsoft says changes take up to 48 hours, and that in Teams the pinning is set through app setup policies.

Microsoft's page makes several points worth knowing before you tell anyone it is fixed.

  • Copilot Chat is pinned by default to the navigation bar of the Microsoft 365 apps. Microsoft also says the pinning setting no longer applies to the Microsoft Copilot app, and that since January 2026 Copilot Chat cannot be unpinned from the navigation for any tenant.
  • "Do not pin" means Copilot Chat is not available by default in Teams and Outlook, though people can add it from their app store.
  • In Teams, you change pinning only through the Teams admin center: add the Copilot app to the pinned apps in an app setup policy and assign it to users with a Microsoft Entra account. You also need to allow the app through an app permission policy.
  • Only users who sign in with a Microsoft Entra account can have Copilot Chat pinned.
  • Unlicensed users can choose to pin or unpin it themselves, and their choice is respected in later sessions.

What should you check in Microsoft Edge?

Microsoft Edge has its own Copilot Chat switches: the Copilot icon appears for people signed in with an Entra account, and admins can restrict it with policies such as HubsSidebarEnabled and EdgeEntraCopilotPageContext. The first disables Copilot Chat in Edge; the second stops it using the open page.

GoalEdge setting Microsoft names
Disable Copilot Chat in Edge entirelyHubsSidebarEnabled policy (this also blocks all Edge sidebar apps)
Stop Copilot Chat in Edge using the open page or PDFEdgeEntraCopilotPageContext policy
Control which sidebar apps show, Copilot Chat includedEdgeMicrosoft365CopilotChatIconEnabled policy
User shows or hides the toolbar buttonEdge > Settings > Appearance > Copilot and Sidebar > Copilot > Show Copilot button on the toolbar
User lets Copilot use browser contentSame page: Allow Copilot to use browser content

If staff report the Copilot icon missing in Edge only, compare these policies before touching Integrated Apps. Microsoft ties the turned-off message to Integrated Apps blocks; the Edge policies remove or restrict the sidebar instead.

Which network and sign-in checks come next?

Microsoft says to allow the whole *.cloud.microsoft domain, make sure rules, URL filters, Conditional Access and app control are not blocking copilot.cloud.microsoft, and instruct staff to sign in with their work account. The green data-protection shield and the Work label show they are in the right experience.

  1. Allow-list. Add *.cloud.microsoft to your allow lists. Microsoft says it does not support allowing only some URLs inside that domain.
  2. Connectivity test. Microsoft links a Microsoft 365 Connectivity test tool for endpoints in the *.cloud.microsoft domain. Run it from an office machine.
  3. Conditional Access and app control. Make sure no policy blocks the Copilot app.
  4. Personal accounts. Do not block copilot.cloud.microsoft to prevent personal sign-in. Microsoft says to use tenant restrictions v2 for that.
  5. Account type. Chats, files and protections stay separate between a work account and a personal Microsoft account, so staff should check for the Work label and the green shield.

Our tutorial on Copilot Chat versus Microsoft 365 Copilot explains what staff get once the app opens, so you can set expectations honestly.

How do you put your company policy on the blocked page?

In the admin center, go to Copilot > Settings > View all > Custom link for blocked Microsoft Copilot app, and enter a URL to your internal guidance. Users then see a link labelled "View info from your organization" on the turned-off page.

This is worth doing whether you plan to unblock everyone or only some people. For people who stay blocked, the link can explain the reason and who to ask. A good internal page is short: why access is limited, who is allowed, how to request it, and the date it will next be reviewed.

How do you roll Copilot Chat out in stages instead of all at once?

A staged rollout uses the same Integrated Apps scoping that caused the problem, but on purpose: allow a small pilot group first, fix what they report, then widen to everyone. It takes a week longer and removes most of the first-day support questions.

Take a second illustration: a mortgage broker with nine staff. The principal wants the three advisers who write the most email to try Copilot Chat before the two administrators and four others, because client files are sensitive. The admin creates a security group named "Copilot pilot", opens the Copilot app in Available Apps, chooses Edit Users, selects "Specific users/group in the organization can install" and adds the group. Microsoft's pages describe exactly this option, and note that unselected users cannot install the app. The pilot group can use Copilot Chat in the Copilot app and Outlook, with Teams following its own app policies; everyone else waits until the principal widens it, so tell them why and when.

WeekAdmin actionWho has accessWhat to collect
1Scope the Copilot app to the pilot group; allow it in Teams for the same three; send the others a two-line note on timing3 advisersWhich tasks they try; any sign-in or network errors
2Fix issues; write the staff message from the template in the last section3 advisersTwo or three tasks that clearly save time
3Change availability to all users; confirm the pinning settingAll 9 staffQuestions staff ask in the first two days
4Review the Copilot Chat usage report in the admin centerAll 9 staffActive users and prompts, to decide whether to keep going

Microsoft's Copilot overview page says the admin center includes a Copilot Chat usage report covering total and daily active users, prompts submitted and average prompts per user over 7, 30, 90 or 180 days. That report is the cheapest way to see whether a switched-on feature is actually used. Our tutorial on the Copilot readiness checklist lists what else to confirm before widening access, and the one on cleaning up SharePoint permissions matters most if you also plan to buy any licences.

Write down what you changed

Admin settings are easy to forget, and the original problem here was a forgotten setting. Keep a one-page change log in the same place as your other admin notes. An illustrative entry looks like this:

22 Nov, 10:15. Integrated apps > Blocked Apps > Copilot.
Before: blocked for group "Production and install" (17 people);
on unblock it reverted to Specific users/group can install (group "Copilot licensed", 5 people).
After: unblocked; All users in the organization can install.
Reason: unlicensed staff saw "Copilot Chat was turned off for your organization".
Also checked: Pin Copilot Chat in Microsoft 365 apps = pinned (default); Teams app permission policy allows Copilot app.
Next check: 24 Nov (pinning can take 48 hours). Owner: [name].

A few lines like these save the next admin an afternoon, and they answer the question "who turned this off?" without anyone needing to be blamed. They also give you the "before" state to return to if the pilot reveals a reason to restrict access again.

How do you tell a real block from a wrong sign-in for one person?

Ask the person to open copilot.cloud.microsoft in a private browser window, sign in with the work account only, and tell you whether they see the Work label and green shield or the turned-off message. This separates a tenant block from a stale sign-in in about two minutes.

Two further checks help when the first one is unclear. Microsoft publishes a Microsoft Copilot service plan diagnostic tool that verifies whether a specific user account meets the requirements for Copilot features, which is useful when a licensed person reports problems. And if the person has both a personal Microsoft account and a work account on the same device, ask them to sign out of both and back in with the work one, because Microsoft states that chats, files, permissions and protections stay separate between the two accounts.

Which mistakes keep Copilot Chat switched off after the fix?

The mistakes that keep Copilot Chat switched off after a fix are changing the wrong setting, testing with a licensed admin account, waiting less than the stated 48 hours for pinning, and forgetting Teams. Each one produces a "still broken" report that is really a partial fix.

The wrong switch. In an illustrative case, an admin turns the general "Let users access Microsoft apps in your tenant" setting back on and nothing changes. Microsoft states that this setting does not turn off the Copilot app, so the app has to be managed directly in the Integrated Apps list.

The licensed tester. The admin tests from a licensed account and sees Copilot working, so reports success. Staff without licences still see the message because the group scoping excluded them. Always test with a representative unlicensed account.

The impatient toggle. A Teams icon does not appear an hour after the pinning change, so the admin flips the setting back and forth. The setting can take up to 48 hours. Change it once, record the time, and check again the next day.

The Teams blind spot. Integrated Apps fixes Outlook and the Copilot app, but Teams honours its own policy. If Teams still hides Copilot, open the Teams admin center and check the app permission policy and the app setup policy.

What should the test checklist after the change include?

Test one unlicensed account and one licensed account on the web, in Outlook, in Teams and in Edge, and tick off each result. A short written checklist turns "it seems to work" into evidence you can show the owner.

TestUnlicensed accountLicensed accountDone
Open copilot.cloud.microsoft in a fresh browser windowChat opens, Work label and green shield visibleSame[ ]
Open Copilot in OutlookCopilot Chat availableSame[ ]
Open Copilot in TeamsAppears after the pinning periodSame[ ]
Edge sidebar iconShows if the Edge policy allows itSame[ ]
Blocked-page link (only for anyone still blocked)"View info from your organization" opens the right pagen/a[ ]
Personal Microsoft account sign-inBehaves as your tenant restrictions intendSame[ ]

If tracking who has been tested and who has been told is the slow part, try The Complete Excel Course with AI Integration on Coding Liquids.

What if you actually want Copilot Chat off for unlicensed staff?

Microsoft's four steps for removing Copilot Chat from unlicensed staff are: unpin it, restrict the Copilot app in Integrated Apps, allow it in Teams only for licensed users, and apply the Edge sidebar policy. Blocking the app in Integrated Apps blocks it tenant-wide, including licensed users.

That last point is the usual trap. If the aim is "licensed users only", do not block the app. Select "Specific users/group in the organization can install" and assign a group of licensed users, then set the Teams policies and the Edge policy to match. Microsoft also warns that users can still reach Copilot Chat from m365.cloud.microsoft/chat even if "Do not pin" is selected, so the Integrated Apps scoping is what actually restricts it. If you reverse the decision later, the fix in this tutorial is the way back.

What should you tell staff once it is working?

Tell staff where to find Copilot Chat, to sign in with their work account, what it is good for, what not to paste, and who to ask. Keep it short enough to read in a minute. This illustrative message can be adapted.

Subject: Copilot Chat is now available

Copilot Chat is switched on for everyone. Open it in Teams, in Outlook, or at copilot.cloud.microsoft.
Sign in with your work account. You should see "Work" under your name and a green shield, which means your chats are covered by our Microsoft agreement.
Good uses: rewriting a rough email, summarising a long message, turning job notes into a clean sheet.
Please do not paste customer bank details, passwords or personal data about staff.
It comes with our Microsoft 365 plan at no extra cost, but some features have fair-use limits; if one stops working, try again later.
Questions or problems: [name]. If you still see "turned off", tell us the time and your account.

The shield and Work label guidance comes from Microsoft's own description of how to tell the work experience from the personal one, and the fair-use line reflects Microsoft's statement that some Copilot Chat features have limits for users without a Copilot licence. Our tutorial on what unlicensed staff can do with uploaded files covers the most common question staff ask next, and the one on rolling out Copilot to a small team covers the wider plan.

Admin questions about switching Copilot Chat back on

Which admin role do I need to unblock the Copilot app?

Microsoft's Integrated Apps page says its controls are available to Global Administrators, while the Copilot pinning setting needs the AI Administrator role. Microsoft recommends the role with the fewest permissions, so use an AI Administrator for pinning and keep Global Administrator for the Integrated Apps change, then sign out of it.

Does turning off 'Let users access Microsoft apps' disable Copilot?

No. Microsoft's Manage Copilot Chat page states that turning off the Let users access Microsoft apps in your tenant setting in Integrated Apps won't turn off the Copilot app. You have to manage the Copilot app directly, which is why the block is easy to miss when you only review the general setting.

How long does the pinning setting take to apply?

Microsoft says changes to Copilot Chat pinning settings take up to 48 hours to go into effect. Test with one account the same day, but tell staff it may take two days to appear in Teams and Outlook, and do not re-toggle the setting while you wait.

Can I block Copilot for some staff and allow it for others?

Yes. Blocking through Integrated Apps is tenant-wide but can be scoped to specific users or groups, including licensed users. To remove access only for unlicensed users, Microsoft suggests limiting who can install the app to a group of licensed users instead of blocking the app for everyone.

Why do some people still see the blocked message after the fix?

Usually because the fix did not reach them. Check that they are not in a group still covered by a block, that the app's availability after the unblock includes them, and that they signed in with the work account rather than a personal one. If the problem is only in Teams, the Teams admin center policies are the next place to look, and a sign-in loop points to the network allow-list instead.

Further reads

Sources: Microsoft Learn pages Manage Copilot Chat, Pin Microsoft Copilot Chat in the Microsoft 365 apps, Apps for Microsoft 365 that work across application hosts, What is Microsoft Copilot? and License options for Microsoft Copilot (all read 22 November 2026).

Ready to put AI on the jobs that eat your week?

No data team or big budget needed. In a 1:1 consultation I show small and medium-sized businesses and self-employed people which AI tools they can use, one workflow at a time.

Book a 1:1 call with me