Integry · Developer platforms · Built on Squig
Microsoft, Google and Meta app verification
Enterprise customers won't connect an app that shows an unverified warning. I worked directly in Microsoft, Google and Meta's developer consoles to set up, verify and keep enterprise-critical connectors approved.
How it works
Microsoft Azure / Entra ID
- App registration: in Entra ID
- Permissions: Microsoft Graph scopes, redirect URIs
- Domain verification: publisher domain
- Verified app: trusted by enterprise tenants
- OAuth consent screen: app details and branding
- Scope selection: justifying each sensitive scope
- Scope verification: Google's review
- Verified app: no unverified-app warning
Meta
- App setup: in Meta for Developers
- Permissions: requesting the scopes the use case needs
- App Review: submission and approval
- Live app: approved scopes in production
What I built
- Microsoft: app registrations in Entra ID, Graph API permissions, and domain verification
- Google: OAuth consent screen setup, scope justification and scope verification
- Meta: app configuration, permission requests and App Review
- Kept connectors approved and working as each platform changed its APIs and policies
Stack
Need something like this?
I'm Muhammad Umar, a senior integration and AI automation engineer with 300+ integrations shipped. Tell me what you want to connect or automate.
Book a 15-minute callNext case study: Daily shipped-work digest