"@odata.context": "https://graph.microsoft.com/v1.0/$metadata#applications/$entity", "id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", "displayName": "My New Application", "replyUrls": ["https://example.com/callback"], "homepage": "https://example.com"
If the response includes @odata.nextLink , use it to fetch the next page. By default, 100 items are returned per page.
If you expose an API ( api.oauth2PermissionScopes ), the default scope user_impersonation is automatically added. Many developers forget to define it, then wonder why "Sign in & read user profile" doesn't work. https- graph.microsoft.com v1.0 applications
headers = "Authorization": f"Bearer access_token" graph_url = "https://graph.microsoft.com/v1.0/applications?$filter=signInAudience eq 'AzureADMyOrg'" response = requests.get(graph_url, headers=headers)
"passwordCredential": "displayName": "AutomatedSecret", "endDateTime": "2025-12-31T23:59:59Z" "@odata
Query for apps with unused delegated permissions:
$applications = Invoke-MgGraphRequest -Method GET -Uri "https://graph.microsoft.com/v1.0/applications?`$select=displayName,appId,passwordCredentials" Many developers forget to define it, then wonder
| Entity | Endpoint | Tenant scope | Analogy | |--------|----------|--------------|---------| | Application | /v1.0/applications | Home tenant only | Blueprint | | Service Principal | /v1.0/servicePrincipals | One per tenant | Built house |
The https://graph.microsoft.com/v1.0/applications endpoint is part of the Microsoft Graph API that allows developers to interact with Azure Active Directory (AAD) applications. This endpoint provides a RESTful interface for creating, reading, updating, and deleting (CRUD) applications in AAD.
]