Connect Microsoft Entra ID to a phone provider for SMS and voice one-time passwords. Guided setup deploys one regional endpoint using JavaScript, C#, or Python.
Start in a separate nonproduction environment and review requirements.
- JavaScript, C#, and Python implementations of one HTTP and trust contract.
- Guided Azure deployment with Easy Auth, Key Vault, and monitoring.
- No-send evaluation for authentication and decryption checks.
- Provider-neutral phone-service integration.
- Confirm provider access and Microsoft's approved test and activation process.
- Prepare a nonproduction tenant, subscription, app registration, and unique resource prefix.
- Check roles, permissions, tools, regional availability, and quota.
- Plan for Azure, telemetry, and provider charges; the cost estimate is not a bill.
- Keep Easy Auth enabled for the approved Microsoft caller.
Easy Auth checks the Microsoft caller before the Function decrypts the request. Live success confirms provider acceptance; confirm delivery separately. Evaluation sends nothing. See architecture details. Open the full-size diagram.
Follow the five-step setup guide in order:
- Get ready: confirm access, approvals, permissions, and budget.
- Register the app: save the tenant and client IDs.
- Deploy: choose the provider, runtime, and plan.
- Connect and test: configure provider access and run approved checks.
- Activate and hand over: activate after validation and assign owners.
Before live use, review production readiness.
- Function monitoring and alerts
- Application Insights collection
- Microsoft Entra ID monitoring
- Certificate renewal and rollback
- Provider cost estimate
- Runtime guides: JavaScript, C#, Python
- Architecture and settings
- HTTP contract
- Log schema
- Phone-service integration
Keep credentials, phone data, OTPs, encrypted bodies, and raw provider responses out of issues and support requests. See the complete documentation index.