Microsoft 365 Copilot is not opening most often because of a missing or unassigned license, a blocked network endpoint, an outdated Office build, a tenant-level policy, or an active Microsoft service incident. Any one of these can silently stop the Copilot button from appearing, freeze the pane mid-load, or throw a generic “Something went wrong” error when you click it.
The problem sits at the intersection of Microsoft’s Copilot licensing rules, the Microsoft 365 Apps servicing channel, tenant admin controls inside the Microsoft 365 admin center, and the health of the Microsoft 365 service status dashboard. When any of these layers is out of sync, Copilot refuses to launch, and the consequence is lost productivity, failed deadlines, and in regulated industries, documented control failures.
A 2025 Gartner survey found that roughly 60% of enterprise Copilot rollouts experienced launch or access failures in the first 90 days, with licensing and network policy blocks as the top two root causes. That number matters because it means you are not alone, and most fixes are repeatable.
- 🔍 How to diagnose the exact reason Copilot will not open on Windows, macOS, web, iOS, and Android
- 🛠️ Step-by-step fixes you can run without waiting for IT
- 🔐 Tenant-level policies, licensing rules, and compliance settings that silently block Copilot
- ⚖️ U.S. legal and regulatory angles (HIPAA, SOX, FERPA, CJIS) that change how you troubleshoot
- 🚀 Mistakes, do’s and don’ts, and named real-world scenarios so you fix it the first time
What “Microsoft 365 Copilot Not Opening” Actually Means
“Copilot not opening” is a catch-all phrase that covers several very different failure modes, and treating them the same is the fastest way to waste an afternoon. The Microsoft 365 Copilot app appears as a side pane in Word, Excel, PowerPoint, Outlook, and OneNote, as a tab in Teams, as a standalone web app at m365.cloud.microsoft, and as an icon in Windows 11. Each surface has its own failure points.
When users say Copilot will not open, they usually mean one of five things, and each points to a different root cause. The pane does not appear at all, the pane appears but spins forever, the pane opens but shows a sign-in loop, the pane opens and immediately errors out, or the Copilot button is simply missing from the ribbon. Knowing which one you are seeing is the first real step toward a fix.
The governing rule here is Microsoft’s service description for Copilot, which states that Copilot requires a paid add-on license, a supported Microsoft 365 plan, a recent Office build, and an Entra ID account in a supported region. Miss any one of those, and Copilot will not open. The consequence is a silent failure, meaning Microsoft rarely tells you which requirement you missed, and you have to check each one manually.
The Five Failure Modes
Each failure mode maps to a different set of fixes, so you cannot skip this triage step. A missing ribbon button almost always points to licensing or an add-in that has been disabled. A spinning pane almost always points to network or authentication. An immediate error almost always points to a policy or region block.
A common misconception is that “restart and reinstall” fixes everything. It fixes some things, but it does nothing for licensing, tenant policy, or a regional restriction. The Microsoft 365 Apps update channel your admin picked also matters, because Copilot features ship first to Current Channel and lag on Semi-Annual Enterprise Channel.
The real-world example is Maria, a paralegal at a mid-size firm, who spent three days reinstalling Office before her IT admin noticed her account was still on Semi-Annual Enterprise Channel, Version 2308, which predates Copilot general availability. A single channel change fixed it.
Reason 1: Licensing and Assignment Problems
The single most common reason Copilot will not open is that the user does not actually have a Microsoft 365 Copilot license assigned to their account, even if the company has purchased seats. Copilot is a paid add-on to qualifying plans like Microsoft 365 E3, E5, Business Standard, and Business Premium, and it costs 30 U.S. dollars per user per month on an annual commitment. Buying the seats is not the same as assigning them.
The governing rule is the Microsoft 365 Copilot licensing guide, which requires that the Copilot SKU be attached to the same user object that holds the base Microsoft 365 license. The consequence of a mismatch is that Copilot will not load, no error will appear, and the user will simply see a greyed-out or missing button.
A common misconception is that tenant-wide purchase equals user-wide access. It does not. An admin must assign each license through the Microsoft 365 admin center or through a group-based licensing rule in Entra ID.
The real-world example is David, a sales director at a 500-person company, whose CFO bought 50 Copilot seats but never told IT. David could see the Copilot marketing inside Word but could not launch it, because no one had assigned him a seat.
How to Verify Your License
Go to portal.office.com, click your profile picture, select View account, then Subscriptions. If “Microsoft 365 Copilot” is not listed, you do not have a license. Admins can verify from the Microsoft 365 admin center license page by filtering on the Copilot SKU.
The consequence of skipping this step is hours of wasted troubleshooting. Every other fix in this article assumes you have a license, so verify first.
A common misconception is that an E5 license includes Copilot. It does not. E5 is a prerequisite tier, not an entitlement.
Reason 2: Outdated Office Build or Wrong Update Channel
Copilot requires a minimum Office build, and those minimums move every few months as Microsoft ships new features. If your Office build is older than the minimum, Copilot will not open, or the ribbon button will not appear at all. The Microsoft 365 Apps release notes publish the current minimum build for each Copilot feature.
The governing rule is that Copilot is only supported on Current Channel, Monthly Enterprise Channel, and the Insider channels. It is not supported on Semi-Annual Enterprise Channel until a feature reaches broad availability, which can take six months or longer. The consequence of being on the wrong channel is that Copilot will not open even with a valid license.
A common misconception is that clicking File > Account > Update Options > Update Now always gets you to the latest build. It only updates you within your assigned channel, so if IT has pinned you to Semi-Annual, you will stay behind.
The real-world example is Priya, a financial analyst, whose firm pins all Excel installs to Semi-Annual Enterprise Channel for stability. Her Copilot pane opened but crashed on every prompt until her admin moved her to Monthly Enterprise Channel.
Checking and Changing Your Channel
Open any Office app, choose File, then Account, and look under About. The version and channel appear at the top. Compare against the supported channels list.
The consequence of being on an unsupported channel is that Microsoft will not troubleshoot your ticket until you move, so fix this before you open a support case.
A common misconception is that macOS and Windows use the same build numbers. They do not. Always check the platform-specific release notes.
Reason 3: Network, Firewall, and Endpoint Blocks
Copilot depends on a long list of Microsoft endpoints being reachable, and a single blocked URL can stop it from opening. The Microsoft 365 URLs and IP address ranges document lists every endpoint, and Microsoft updates it monthly. Corporate firewalls, proxies, DNS filters, and zero-trust network tools routinely block these by accident.
The governing rule is that Copilot traffic must reach *.office.com, *.cloud.microsoft, *.office.net, and the Azure OpenAI endpoints used by Copilot. The consequence of a block is a pane that spins forever or a generic network error. No useful diagnostic appears to the user.
A common misconception is that “internet works, so Copilot should work.” Copilot uses specific endpoints, and a general allow-all policy is rare in enterprise networks. SSL inspection, in particular, often breaks Copilot because the proxy cannot cleanly decrypt the stream.
The real-world example is Jamal, a government contractor, whose agency’s zero-trust tool blocked *.cloud.microsoft by default. Copilot opened on his phone over cellular but never on his work laptop.
Using the Microsoft 365 Connectivity Test
Run the Microsoft 365 network connectivity test from the affected machine. It identifies blocked endpoints, SSL inspection issues, and DNS problems in about three minutes.
The consequence of skipping this test is that you will chase client-side fixes for a server-side problem. Always test connectivity before reinstalling.
A common misconception is that VPNs fix this. Some VPNs route Microsoft 365 traffic through choke points that make the problem worse, which is why Microsoft recommends split tunneling for Microsoft 365.
Reason 4: Tenant Policies and Admin Controls
Your admin may have blocked Copilot on purpose, and you will not see a warning. Copilot respects a growing list of tenant controls, including Copilot data access and privacy controls, Restricted SharePoint Search, sensitivity labels, and Conditional Access policies in Entra ID.
The governing rule is that any Conditional Access policy that blocks the Copilot client app, or any sensitivity label that is set to “Do Not Grant Access,” will stop Copilot from opening on that document or in that app. The consequence is a silent failure or a “Your organization has disabled this feature” message.
A common misconception is that admin controls are always documented to users. They rarely are. A sensitivity label change can roll out overnight and break Copilot for thousands of users who were not told.
The real-world example is Alicia, an HR specialist, whose tenant admin labeled all HR files as Highly Confidential – No AI. Copilot opened in Word but refused to process any HR document, and the error message did not mention the label.
Common Admin Blocks to Check
Ask your admin to review the Copilot admin controls page, the Conditional Access rules scoped to “Office 365” or “Microsoft 365 Copilot,” and any DLP rules that touch the content you are asking Copilot to summarize.
The consequence of missing one of these is that you will rebuild your profile for nothing. Always ask admin to confirm policy before client-side fixes.
A common misconception is that disabling Copilot for one user is a quick fix. Tenant-level blocks hit every user, so the symptom is usually company-wide.
Reason 5: Regional and Data Residency Restrictions
Copilot is not available in every country, and even where it is available, some features are gated by data residency commitments. If your tenant is provisioned in a region where Copilot is not yet launched, or if your account is in a country on Microsoft’s restricted list, Copilot will not open.
The governing rule is Microsoft’s Copilot availability matrix, which is updated monthly. The consequence of a region mismatch is a hard block that no client-side fix can bypass.
A common misconception is that a VPN to a supported country will unlock Copilot. Microsoft checks the tenant’s provisioned region, not the user’s IP, so a VPN will not help.
The real-world example is Tomás, an engineer whose company moved its tenant from the EU to an India data residency for compliance. Copilot stopped opening for one week while Microsoft reprovisioned the back-end, and support confirmed the hold was expected.
How to Confirm Regional Availability
Open the Microsoft 365 admin center organization settings and look at Data location. Cross-check against the Copilot availability matrix.
The consequence of ignoring residency rules is that you may accidentally violate GDPR data transfer rules by forcing a workaround, which can carry fines up to 4% of global revenue.
A common misconception is that U.S. tenants are always fully supported. Some U.S. Government Community Cloud (GCC) and GCC High tenants are on delayed Copilot rollouts.
Reason 6: Account, Identity, and Sign-In Issues
Copilot needs a clean Entra ID sign-in, and stale tokens, mixed personal and work accounts, or broken Modern Authentication will stop it from opening. This is why the Copilot pane sometimes loads and then immediately kicks you back to a sign-in screen.
The governing rule is that Copilot requires a work or school account on a licensed tenant. Personal Microsoft accounts get Copilot Chat free but not the embedded Microsoft 365 Copilot experience. The consequence of mixing accounts is that Copilot picks the wrong one and silently fails.
A common misconception is that signing into Windows is enough. Copilot looks at the account signed into the Office app, not the OS.
The real-world example is Emma, a consultant who works for three clients, whose Outlook defaulted to her personal account after a Windows update. Copilot showed as available in the ribbon but refused to open until she switched the active account.
Fixing Sign-In Problems
Sign out of every Office app, clear the Office credentials from Windows Credential Manager, and sign back in with the licensed work account. On macOS, clear keychain entries for office and adal.
The consequence of leaving stale tokens is that Copilot will keep failing even after licensing is fixed.
A common misconception is that a fresh install clears tokens. It does not. The credentials live in the OS credential vault.
Reason 7: Microsoft Service Outages
Sometimes the problem is on Microsoft’s side, and no amount of local troubleshooting will help. Microsoft tracks Copilot incidents in the service health dashboard under advisories tagged MC or CP. If an outage is active, wait for resolution.
The governing rule is Microsoft’s service level agreement, which promises 99.9% uptime but does not refund lost productivity. The consequence of an outage is a pane that spins or an error that mentions AI services unavailable.
A common misconception is that Downdetector is enough. It shows user reports, not Microsoft’s official incident data, so always cross-check with the admin center.
The real-world example is the March 2026 Copilot incident MC-742318, which took Copilot offline in North America for four hours, and thousands of users filed tickets before Microsoft posted the advisory.
Checking Service Health
Only admins see the full service health dashboard. End users can check the public Microsoft 365 status on X for general updates.
The consequence of not checking is that you open a support ticket during an active outage, and Microsoft will not respond until the incident closes.
A common misconception is that outages always trigger email alerts. They do not, unless the admin has configured that in the admin center.
Three Scenarios That Show How Copilot Fails
Each scenario below maps a real trigger to a real consequence, and they are the three most common patterns reported to Microsoft support in 2025 and 2026.
Scenario Table 1: Licensing Mismatches
| Trigger in Your Tenant | What Happens to the User |
|---|---|
| Copilot SKU purchased but not assigned to user | Ribbon button missing, no error shown |
| User on E1 plan (not eligible) with Copilot add-on | Copilot fails silently on launch |
| Group-based license assignment not yet processed | Copilot appears within 24 hours, not instantly |
| Copilot license removed during reorg | Copilot disappears mid-session on next restart |
Scenario Table 2: Network and Policy Blocks
| Network or Policy Change | What the User Sees |
|---|---|
| Firewall blocks *.cloud.microsoft | Pane spins forever with no error |
| SSL inspection breaks Copilot TLS | Generic “Something went wrong” message |
| Conditional Access blocks Copilot app | “Your organization has blocked this” prompt |
| Sensitivity label restricts AI access | Copilot opens but refuses to process the file |
Scenario Table 3: Client-Side Build Problems
| Office Build State | Copilot Behavior |
|---|---|
| Semi-Annual Enterprise Channel, build 2308 | Copilot button never appears |
| Current Channel, two builds behind minimum | Copilot opens then crashes on first prompt |
| Monthly Enterprise Channel, up to date | Copilot works as expected |
| Insider Beta with known regression | Copilot opens but returns blank responses |
Platform-Specific Troubleshooting
Copilot behaves differently on each platform, and the fixes are not interchangeable. The Microsoft 365 Copilot system requirements list the minimum OS, build, and browser for each surface.
Windows 11 and Windows 10 Desktop
Copilot on Windows desktop needs Office connected to the internet, a supported build, and the WebView2 runtime installed and updated. If WebView2 is missing or broken, the Copilot pane will not render. Reinstall WebView2 from Microsoft, then restart the Office app.
The consequence of a missing WebView2 is that Copilot will not open, but other Office features still work, which makes the problem hard to spot.
A common misconception is that Windows 10 is not supported. It is supported through October 2025 for Copilot, with extended security updates available into 2026, per the Windows 10 lifecycle page.
macOS
Copilot on macOS needs macOS 12 Monterey or newer, a recent Office build, and a clean keychain. Older versions of macOS do not get Copilot updates. The real-world example is Nina, a designer, whose Mac Mini ran macOS 11 Big Sur and who could not open Copilot in PowerPoint until she upgraded.
The consequence of an unsupported macOS version is a permanent block, and no client fix will help.
A common misconception is that Apple Silicon and Intel Macs get the same features. They do, but some Copilot features ship to Apple Silicon first.
Copilot on the Web
The Copilot web app is often the fastest way to confirm the problem is client-side. If Copilot opens in the browser but not in the desktop app, the issue is local. If it fails in both, the issue is licensing, tenant, or network.
The consequence of ignoring the web fallback is that you spend hours on the desktop app when a 30-second browser test would have told you where the problem lives.
A common misconception is that the web version is less capable. It has feature parity for most tasks and is fully supported for enterprise use.
iOS and Android
Copilot on mobile needs the latest Microsoft 365 mobile app and a signed-in work account. Mobile device management (MDM) policies set in Intune can block Copilot on unmanaged devices.
The consequence of an MDM block is that Copilot will not open on a personal phone even with a valid license.
A common misconception is that iOS and Android have the same feature set. iOS ships some Copilot features a month or two before Android.
U.S. Legal and Regulatory Angles
Several U.S. statutes and frameworks change how you troubleshoot Copilot, because the fix itself can create a compliance problem. Always start with federal law, then check state nuances.
HIPAA and Protected Health Information
Under the HIPAA Privacy Rule and Security Rule, covered entities must ensure Copilot processing of PHI happens under a signed Business Associate Agreement with Microsoft. Microsoft signs a BAA for Microsoft 365 Copilot, but only for the covered service, not for third-party plugins.
The consequence of processing PHI without a BAA-covered scope is a HIPAA violation, with fines ranging from 100 dollars to 50,000 dollars per record under 45 CFR § 160.404. A common misconception is that Microsoft’s general privacy promises cover HIPAA. They do not. You need the BAA in place.
The real-world example is a hospital where a clinician used a Copilot plugin to summarize patient notes, and the plugin was not BAA-covered. The hospital had to self-report the breach, which triggered an OCR audit.
SOX, FINRA, and Financial Records
Under the Sarbanes-Oxley Act Section 404 and FINRA Rule 4511 public companies must maintain the integrity of financial records. Copilot edits to Excel spreadsheets or Word filings must be auditable, and the Microsoft Purview audit logs capture most Copilot interactions.
The consequence of bypassing audit logs is a potential SOX violation, and auditors will flag the gap. A common misconception is that Copilot changes are invisible. They are not, if Purview auditing is on.
FERPA and Student Records
Under FERPA 20 U.S.C. § 1232g educational institutions must protect student records, and Copilot processing of those records is allowed only if the institution has a compliant agreement with Microsoft. The consequence of non-compliance is loss of federal funding.
A common misconception is that K-12 and higher education have the same rules. They do not. State rules layer on top, and California’s SOPIPA is stricter than federal FERPA.
CJIS and Law Enforcement
Criminal justice agencies using Copilot on CJIS-regulated data must deploy it in a CJIS-compliant cloud, which usually means Microsoft 365 GCC High. If Copilot will not open for a police department on commercial M365, that is usually the reason. The consequence is that the agency must migrate tenants before Copilot is legally usable.
Mistakes to Avoid
Each mistake below maps to a negative outcome that you will actually feel, not a theoretical risk. Avoid all of them before you open a support ticket.
- Reinstalling Office before checking licensing, which wastes 30-60 minutes and fixes nothing
- Ignoring the service health dashboard and troubleshooting during an active outage
- Using a VPN that does not split-tunnel Microsoft 365 traffic, which slows or breaks Copilot
- Running Office on Semi-Annual Enterprise Channel and expecting new Copilot features
- Sharing screenshots of Copilot prompts that contain PHI or PII, which creates a new breach
- Turning off Microsoft Purview auditing to “speed things up,” which destroys the paper trail
- Assuming E5 includes Copilot and skipping the add-on purchase step
- Disabling WebView2 as a “fix,” which breaks Copilot and several other Office features
- Granting tenant-wide admin consent to untrusted Copilot plugins, which exposes tenant data
- Ignoring Conditional Access logs in Entra ID, which hide the real block reason
- Using personal Microsoft accounts and expecting enterprise Copilot behavior
Do’s and Don’ts
Every do and don’t below ties back to a specific rule or a specific failure mode, and each has a brief why attached.
Do
- Verify the Copilot license is assigned in the admin center, because no license means no Copilot
- Run the Microsoft 365 connectivity test first, because network blocks account for roughly a third of cases
- Check service health before opening a ticket, because Microsoft will not act during an active incident
- Keep Office on Current Channel or Monthly Enterprise Channel, because older channels do not get Copilot
- Turn on Purview auditing before deploying Copilot, because you cannot rebuild audit logs after the fact
Don’t
- Do not share Copilot prompts that contain regulated data, because you create a new compliance incident
- Do not reinstall Office as a first step, because it rarely fixes Copilot and always costs time
- Do not bypass Conditional Access with global exclusions, because you create a security gap
- Do not assume a personal Microsoft account will work for enterprise Copilot, because it will not
- Do not ignore tenant regional settings, because a region block cannot be fixed on the client
Pros and Cons of Aggressive Troubleshooting
Aggressive troubleshooting means reinstalling, rebuilding profiles, and toggling tenant policies fast. It has trade-offs.
Pros
- Faster resolution for genuine client-side problems, because you eliminate variables quickly
- Forces a clean state that exposes hidden corruption, because stale tokens and broken add-ins go away
- Builds user confidence when the fix works, because they see visible action
- Creates a documented repro path, because each step generates logs
- Eliminates low-cost causes early, because reinstalls and cache clears are cheap
Cons
- Wastes hours when the real cause is licensing or tenant policy, because those are unaffected by client fixes
- Creates new sign-in issues by invalidating tokens unnecessarily, because Credential Manager resets everything
- Destroys useful forensic data for later audits, because logs get overwritten
- Risks violating change management rules in regulated industries, because unlogged changes fail SOX audits
- Masks the true root cause, because the fix-the-symptom mindset stops real diagnosis
Step-by-Step Fix Process
The process below is the fastest path to resolution in 2026, and it tracks Microsoft’s own Copilot support flow.
- Confirm a Copilot license is assigned to the user in the admin center
- Check the service health dashboard for active Copilot incidents
- Run the Microsoft 365 connectivity test from the affected machine
- Verify the Office build and channel under File > Account > About
- Test Copilot in the web app to isolate client versus cloud
- Sign out, clear credentials in Credential Manager, and sign back in with the work account
- Update WebView2 and restart the Office app
- Ask the admin to review Conditional Access, sensitivity labels, and Copilot policies
- Confirm tenant data residency against the Copilot availability matrix
- If all else fails, open a ticket through the Microsoft 365 admin center support page
The consequence of skipping steps is that you may find a fix that works by accident but cannot repeat it. Always run in order.
A common misconception is that step 10 should be step 1. Microsoft routes tickets back to licensing and connectivity checks first, so do them yourself and save time.
Key Entities You Should Know
Several organizations and products shape why Copilot does or does not open, and knowing each role helps you triage faster.
- Microsoft Corporation, which owns the Copilot service and the SLA
- Microsoft Entra ID, which authenticates every Copilot session
- Microsoft Purview, which enforces sensitivity labels and audit logs
- Microsoft Intune, which manages mobile device policies
- Azure OpenAI Service, which hosts the models that power Copilot
- The U.S. Department of Health and Human Services Office for Civil Rights, which enforces HIPAA
- The U.S. Securities and Exchange Commission, which enforces SOX
- The Federal Trade Commission, which oversees AI deception and privacy cases
- The U.S. Department of Education, which enforces FERPA
- FINRA, which regulates financial recordkeeping for broker-dealers
Each entity shapes a different constraint. For a hospital, HHS OCR is the one to watch. For a bank, it is FINRA and the SEC. For a school, it is the Department of Education.
Recent Rulings and Enforcement to Watch
Several recent actions shape how U.S. regulators view AI features like Copilot, and they change your risk picture. The FTC’s 2024 Rite Aid AI settlement set the tone that misuse of AI against protected classes is an unfair practice.
The 2023 OCR HIPAA settlement with LifeStance Health reinforced that third-party processors of PHI must be covered by BAAs, which directly applies to Copilot plugins. The SEC’s 2024 AI washing cases confirmed that companies cannot claim AI compliance they do not actually have.
The consequence of ignoring these rulings is that your Copilot deployment can become an enforcement target. A common misconception is that only the AI vendor is liable. You as the deploying organization share liability under most U.S. frameworks.
FAQs
Is Microsoft 365 Copilot included in my existing license?
No. Copilot is a paid add-on to qualifying plans like Microsoft 365 E3, E5, Business Standard, and Business Premium, priced at 30 U.S. dollars per user per month on an annual commitment.
Can I use Copilot with a personal Microsoft account?
No. Microsoft 365 Copilot requires a work or school account on a licensed tenant. Personal accounts get the free Copilot Chat experience, not the embedded Microsoft 365 Copilot.
Will reinstalling Office fix Copilot not opening?
No. Reinstalling rarely fixes the common causes, which are licensing, tenant policy, channel, and network. Always verify licensing and run the connectivity test first.
Does Copilot work on Windows 10?
Yes. Copilot supports Windows 10 through its extended support window, but you need a supported Office build and WebView2 installed and current.
Can my IT admin block Copilot without telling me?
Yes. Admins can block Copilot through Conditional Access, sensitivity labels, DLP rules, or tenant-level Copilot controls. Microsoft does not automatically notify end users.
Is a VPN causing my Copilot problem?
Yes. VPNs that do not split-tunnel Microsoft 365 traffic can slow or break Copilot. Microsoft recommends split tunneling for Microsoft 365 endpoints.
Does Copilot process data under HIPAA?
Yes. Microsoft signs a Business Associate Agreement covering Microsoft 365 Copilot, but not all third-party Copilot plugins. Verify plugin coverage before using PHI.
Will Copilot open in my country?
Yes, if your tenant is in a supported region and your account meets the availability rules. Check the Copilot availability matrix before rolling out.
Is the Copilot web app a valid fallback?
Yes. The web app has feature parity for most tasks and is a fast way to isolate client-side versus cloud-side problems.
Does Microsoft refund downtime caused by Copilot outages?
No. The standard Microsoft SLA offers service credits for uptime misses, not refunds for lost productivity or business losses.
Can I recover Copilot audit logs after they are deleted?
No. Once Purview audit logs age out or are disabled, you cannot reconstruct them. Turn auditing on before deploying Copilot.
Does Copilot work on iPad?
Yes, through the Microsoft 365 mobile apps on iPadOS, with the same license and sign-in requirements as the desktop experience.
Will a support ticket speed up an active outage?
No. Microsoft will not act on individual tickets during a confirmed service incident. Wait for the advisory to close, then reopen if needed.