The short answer
By default, Microsoft lets users approve some apps themselves. In Microsoft's words, all users are allowed to consent to applications for permissions that don't require administrator consent, and its example is an app accessing a user's mailbox. So an AI note taker can reach someone's email without IT ever seeing a request.
Step 1: List what's connected
In the Microsoft Entra admin center, open Enterprise apps. Review each app's permissions and who granted them. Note the ones that:
- can read mail, files, chats or meetings
- work with nobody signed in
- were approved for the whole organization
- come from a publisher Microsoft hasn't verified
Step 2: Rank by risk
Not every app deserves the same attention. An app that reads every file in the company with nobody signed in comes first. An app that only knows a user's name comes last. Ask what each app can reach, not just what it's called, because names can mislead. Microsoft warns against relying on application names and domain URLs as a source of authenticity.
Step 3: Tighten who can approve apps
Microsoft recommends allowing user consent only for apps from a verified publisher. You'll find the setting in the Entra admin center, under Enterprise apps, Consent and permissions, User consent settings. Turn on the admin consent workflow as well, so staff can request an app rather than work around you.
Verification isn't a guarantee. Microsoft says it's still important to review what a verified app is asking for.
Step 4: Clean up what's already there
This step is easy to miss. Microsoft notes that changing consent settings only affects future approvals, and existing grants remain unchanged. Tightening the setting doesn't remove anything, so you must remove old access yourself.
Step 5: Keep checking
Microsoft advises routinely auditing apps and consented permissions. New AI tools appear constantly, so one review goes out of date quickly.
The faster way
Doing this by hand takes time. The free AI report lists every app connected to your Microsoft 365, ranks each by risk, and explains in a plain sentence what it's allowed to do. It doesn't read any email, files or chats. See a sample.
Sources: Configure how users consent to applications, Microsoft Learn | Protect against consent phishing, Microsoft Learn