Uncovering Shadow IT in Your Microsoft 365 Tenant

By Mirko Peters · 2026-08-11

Welcome back to the podcast and our companion deep-dive blog! If you have ever wondered what is really happening beneath the surface of your Microsoft 365 environme…

Welcome back to the podcast and our companion deep-dive blog! If you have ever wondered what is really happening beneath the surface of your Microsoft 365 environment, you are not alone. Many organizations operate under the assumption that because they are in the cloud, everything is neat, tidy, and secure. Unfortunately, the reality of modern enterprise collaboration often resembles a digital Wild West. Employees want to get things done quickly, and in doing so, they frequently hook up external tools, share links far and wide, and grant permissions they shouldn't. This creates massive visibility gaps and leaves sensitive corporate data exposed to unknown threats.

Today, we are expanding on our recent discussions about securing your modern workspace. If you haven't listened to it yet, make sure to check out the related episode, Connect Internal Data to Microsoft 365 Copilot Safely, where we break down how unmanaged data and invisible third-party apps can turn your brilliant AI rollout into a security nightmare. In this post, we are going to walk through a practical, step-by-step playbook to track down unknown apps, tackle risky OAuth scopes, control guest-installed connectors, and establish a clean review loop using Microsoft-native tools.

What Chaos Looks Like

To fix a problem, you first have to look it in the eye. When we audit Microsoft 365 tenants, we rarely find a pristine ecosystem. Instead, we typically uncover a specific blend of digital chaos that accumulates organically over months and years. Here is what that chaos actually looks like:

• Surprise Teams bots and Power Automate connectors tied to personal services.

• Over-shared SharePoint links (“anyone can view”) and unknown external guests.

• Broad OAuth scopes (e.g., Read all mailboxes) granted by well-meaning users.

• Orphaned apps owned by ex-employees still syncing sensitive data.

When users connect a helpful calendar tool or an automated workflow application to make their days easier, they rarely consider the underlying security implications. They simply click "Accept" on a consent prompt. Multiply that by hundreds or thousands of employees, and you have a massive invisible attack surface.

🔎 The Hunt: Native Tools That Surface Shadow IT

The good news is that you don't necessarily need to buy expensive third-party platforms to find this exposure. Microsoft provides robust native tooling that can surface shadow IT right out of the box. Here are the core tools you should use to start your investigation:

• Microsoft Defender for Cloud Apps (MCAS) Shadow IT discovery: traffic, app risk scores, usage trends.

• Entra ID (Azure AD) Sign-in & Audit logs: who consented, when, from where, to what scopes.

• Enterprise Apps → Permissions: enumerate admin-consented and user-consented apps.

• Power Platform Admin Center: unmanaged Power Automate connectors & flows.

• SharePoint/OneDrive reports: anonymous links, external sharing hotspots.

Pro tip: Start with apps requesting tenant-wide scopes (Mail.Read, Files.Read.All, Sites.Read.All, offline_access) and apps installed by guests.

🧱 Draw the Line (Without Breaking Workflows)

Once you have uncovered the shadow IT in your tenant, your immediate impulse might be to hit a massive "Block All" button. Do not do this. If you completely break user workflows overnight, you will face an adoption rebellion, and employees will simply find cleverer, less visible ways around your controls. Instead, you need to implement smart guardrails that protect the organization while keeping productivity high.

• App Consent Policies

  • Block user consent by default; allow only verified publishers and low-impact scopes.

  • Route higher-risk requests to an IT approval workflow (ServiceNow/Power Automate).

• Conditional Access for Apps

  • Require MFA, compliant devices, and trusted locations for risky app access.

  • Block legacy/unsupported client types; exclude meeting rooms/service accounts appropriately.

• Govern Power Platform

  • Data Loss Prevention (DLP) policies: split Business vs Non-Business connectors.

  • Turn on solution-aware flows; restrict custom connectors.

• External Sharing Guardrails

  • Default to people in your org; require expiry for guest links; sponsor model for guests.

🛠️ One-Week Remediation Sprint (Practical Playbook)

Trying to tackle governance all at once can lead to analysis paralysis. To make this manageable, follow this structured, one-week remediation sprint to get your arms around tenant security:

Day 1–2: Discovery

• Pull MCAS Shadow IT report & Entra ID app permissions export.

• Flag admin-consented apps + tenant-wide scopes + guest-owned apps.

Day 3: Contain

• Set User consent = Disabled (or verified publishers, low-risk only).

• Create Conditional Access (per-app): MFA + compliant device for risky scopes.

Day 4: Clean

• Revoke unused/orphaned apps; contact owners for critical flows; migrate if needed.

• Tighten SharePoint external sharing & link expiry defaults.

Day 5: Govern

• Roll out request/approval workflow for new apps.

• Publish allowed app catalog + “request an exception” form.

Day 6–7: Monitor & Communicate

• Turn on anomaly alerts (new high-risk consent, unusual sign-ins).

• Send a friendly “How to request an app” guide; list blocked behaviors & alternatives.

🧪 Policy Templates (Quick Starts)

To help you jumpstart your configuration work, here are two quick-start policy templates you can implement in your test environments today:

• App Consent Policy:

  • Allow: Verified publisher + scopes in baseline list (openid, profile, email, offline_access only).

  • Require approval: Any Mail.Read*, Files.Read*, Sites.Read*, Chat.Read*, Calendars.ReadWrite, Directory.Read.All.

  • Deny: Mail.ReadWrite, Files.ReadWrite.All, full_access_as_app.

• Conditional Access (per-app):

  • Target cloud apps = risky OAuth app.

  • Grant = MFA + compliant device; Block from high-risk sign-ins / unknown countries.

📊 KPIs That Prove It’s Working

Security is a journey, not a destination, and leadership will eventually want to know if your efforts are paying off. Use these key performance indicators to track and report your progress:

• Shadow apps discovered → sanctioned/blocked ratio (target: >80% resolved in 30 days).

• New user-consented apps per month (target: near zero; all via workflow).

• High-risk scopes granted (target: 0).

• External sharing with “anyone” links (target: -90% in 60 days).

• Incidents tied to third-party apps (target: -40% QoQ).

🧾 Review Cadence (Keep It Clean)

Cleaning your tenant once is not enough. Without a recurring operational cadence, shadow IT will creep right back in within a few months. Build these review loops into your regular IT operations:

• Monthly: New consents, high-risk scopes, orphaned owners, guest app installs.

• Quarterly: DLP policy drift, Power Platform environment audit, external sharing report.

• After Org Changes: Reassign app ownership; re-validate app purpose & scopes.

🧯 Fast Troubleshooting Map

When an alert pops up or a user runs into a roadblock, you need quick answers. Keep this troubleshooting map handy for your helpdesk and security operations teams:

• “Where did this app come from?” → Entra ID > Enterprise Apps > Audit logs (ConsentGranted).

• “Why did mail suddenly leak?” → Check app scopes for Mail.* + audit MailItemsAccessed.

• “Guest connected a tool?” → Filter apps by Owner = Guest; revoke & sponsor request path.

• “Flow hitting personal services?” → DLP policy catching Non-Business connector; migrate or sanction.

🧠 Change Management That Users Don’t Hate

Technology controls are only half the battle. Successful security relies heavily on cultural alignment. If you make life difficult for your users, they will actively work against your controls. Make change management smooth by focusing on enablement:

• Publish an App Catalog (approved tools + data boundaries).

• Offer secure alternatives before blocking popular apps.

• Keep a 1-page request guide (what info to provide; expected SLA).

• Celebrate “sanctioned wins” (e.g., replacing a risky connector with a secure, supported one).

✅ Executive Takeaways

Uncovering shadow IT in Microsoft 365 can feel intimidating at first glance, but it is an entirely solvable challenge when approached methodically. Keep these core takeaways in mind as you present your plans to leadership:

• Shadow IT is inevitable; unmanaged risk is optional.

• Use built-in Microsoft tooling for 80% of discovery & control.

• Workflow > wall: approvals keep productivity up while cutting risk.

• Track a few KPIs and show quarter-over-quarter risk reduction.

By taking control of your tenant's app consents, auditing external shares, and implementing clear governance pathways, you protect your company's most sensitive data without stifling innovation. To hear more about how these security measures tie into modern productivity tools like AI, make sure you listen to the full episode over at Connect Internal Data to Microsoft 365 Copilot Safely. Stay secure, keep testing, and we will see you in the next episode!