Summary User stuck on M365 admin-consent flow. Connection expired after 10 min. Need Composio's Azure app client_id to give the tenant admin the direct adminconsent URL. Emailed support + security — no response in 5 days. Setup - Auth config: freya-outlook-mail (ac_VKamXv4yogM5) — Composio-managed OAuth - User: tvalantin@myhomeconnexion.com (MHC tenant — "Admin approval required" enabled) - Connection: ca_r_-SyFV6E_2P — EXPIRED ("did not complete within 10 minutes") What happened 1. Tom starts Outlook OAuth — hits admin-consent wall 2. Connection expires before admin can approve 3. Tenant admin searches Entra for "Freya" — finds nothing (consent screen shows "Composio") 4. We can't build the adminconsent URL without Composio's Azure client_id:

https://login.microsoftonline.com/{tenant_id}/adminconsent?client_id=???

Three questions 1. What is Composio's Azure app client_id for the managed Outlook integration? 2. Where should the admin look in Entra — "Enterprise Applications" (search "Composio") or "Admin consent requests"? 3. After consent is granted, can Tom retry immediately or does anything need resetting on Composio's side? (Same user has 4 stale ACTIVE Outlook connections — should we delete them first?)

Hi there, Sorry for the delay getting back to you, and for the trouble at the consent wall. Quick clarification first: the managed app shows up as "Composio" on the consent screen, not "Freya" (that's just your auth config name), so the admin should search "Composio" in Entra. You also don't need a hand-built adminconsent URL to unblock this. To grant consent, any one of these works: • Entra > Enterprise applications > search "Composio" > Permissions > grant admin consent for the org. • If Tom's attempt raised a request, the admin can approve it under Entra > Admin consent requests. • Or have the admin run the connect flow once and use the in-flow "sign in as an admin" option to consent for the org. Heads up: that attempt connects the admin's mailbox, so Tom should start a fresh connection afterward. On the client_id: since it's our managed app, I don't want to hand you an identifier I haven't confirmed is current, so let me verify that internally before sharing. If you'd rather own the whole flow (your own

client_id

plus tenant restriction), you can switch the auth config to "Use your own developer authentication" and register your own Azure app, then use that app's

client_id

and tenant in the adminconsent URL. On your last question: • The expired attempt (

ca_r_-SyFV6E_2P

) can't be resumed (incomplete Outlook attempts expire after about 10 minutes), so Tom just starts a fresh connect once consent is granted. Nothing needs resetting on our side. • The 4 stale active connections won't block a new connection; cleaning them up is optional. Just reply here if anything's still off and I'll loop in the right person on the client_id. This response was generated automatically by Composio's AI support agent. If it doesn't fully resolve your issue, or you'd like to speak with a person, just reply here and a member of our team will take a look.