Skip to main content
Version: Insiders

Get Owner Permissions

Professional

The EasyLife 365 Identity Insiders API lets you read what the technical owners and business owners of an application are allowed to do. The answer shows the same permissions an application owner sees on the application's Settings page, each one either granted (true) or not (false).

The response carries appType, technicalOwners and businessOwners, which is exactly what Update Owner Permissions reads. You can send it back unchanged, or keep it in source control and edit it there. The update request ignores the other properties.

Permissions​

Permission TypePermissions (Scope)
Delegated (work or school account)https://api.insiders.easylife365.cloud/admin/Config.ReadWrite.All
Applicationhttps://api.insiders.easylife365.cloud/admin/Identity.Ownership.Read.All, https://api.insiders.easylife365.cloud/admin/Identity.Ownership.ReadWrite.All, https://api.insiders.easylife365.cloud/admin/Identity.Manage.ReadWrite.All
note

Any one of the listed application permissions grants access to this endpoint. Application permissions always require admin consent. See Create Application Registration for the app-only setup.

HTTP Request​

GET https://api.insiders.easylife365.cloud/admin/identity/v1/apps/{id}/ownership/permissions?type={app-type}
ParameterDescription
idThe Entra Object ID of the application registration or enterprise application. Not its Application (client) ID.
typeappRegistration or enterpriseApplication. Required.

HTTP request headers​

HeaderValue
Authorization****** (Required)

Request Body​

This request does not require or support any data.

Response​

A successful request returns 200 OK with this body.

PropertyTypeDescription
app.objectIdStringThe Entra Object ID of the application.
app.appIdStringThe application's Application (client) ID.
app.displayNameStringThe application's display name.
app.typeNumber0 for an app registration, 1 for an enterprise application.
app.isManagedBooleanWhether EasyLife 365 Identity Insiders tracks the application as managed. Scans maintain this value, so it can lag a recent change.
appTypeNumberThe same value as app.type, where Update Owner Permissions expects it.
technicalOwnersObjectEach technical owner permission, with true when it is granted. See Permission names.
businessOwnersObjectEach business owner permission, with true when it is granted.
warningsArrayGranted permissions that cannot take effect yet, each with a code and a message. Empty when there is nothing to warn about.

Permission names​

Each name matches a box on the application's Settings page.

NameSettings page labelApplies to
editCredentialsChange certificates and secretsTechnical owners
editOwnersChange app ownersTechnical owners
editTechnicalOwnersChange technical ownersTechnical owners
editSettingsChange app settingsTechnical owners
editBusinessOwnersChange business ownersTechnical owners and business owners
extendActivityExtend app activityTechnical owners, enterprise applications only
editPropertiesChange app propertiesTechnical owners, enterprise applications only

An app registration has five technical owner permissions, and an enterprise application has all seven. Business owners have one permission, editBusinessOwners, on both.

An application whose settings were never saved shows the defaults its Settings page shows: on an enterprise application, extendActivity is granted. Get Application Ownership reports no permissions for such an application, so read owner permissions from this endpoint.

Warnings​

CodeMeaningWhat to do
EL0006editCredentials, editOwners or editProperties is granted, but the EasyLife 365 Identity Insiders service principal is not an owner of the application. Technical owners cannot use these permissions until it is.Add the EasyLife 365 Identity Insiders service principal as an owner of the application. See Make the target application managed.

Errors​

Errors are application/problem+json. Read code. See Errors for the format.

StatuscodeWhen
400 Bad RequestInvalidPayloadtype is missing or not one of the two values. The detail explains which.
401 UnauthorizedAuthenticationRequiredThe token is missing, expired or for another API.
403 ForbiddenNotAllowedThe token does not carry one of the permissions above.
403 ForbiddenIdentity.LicenseRequiredThe tenant does not have a Professional or Trial license.
404 Not FoundNotFoundNo application with this Object ID and type exists in your tenant.
429 Too Many RequestsnoneToo many requests. The answer is a short text with a Retry-After header, not a JSON body. Wait and retry. This route uses the limit for read calls.

Example 1: Read the owner permissions of an enterprise application​

This example reads the owner permissions of the enterprise application with Object ID 8f3c2a71-5d4e-4b9a-a1c6-2e7f90d4b5a3.

Request​

GET https://api.insiders.easylife365.cloud/admin/identity/v1/apps/8f3c2a71-5d4e-4b9a-a1c6-2e7f90d4b5a3/ownership/permissions?type=enterpriseApplication

Response​

{
"app": {
"objectId": "8f3c2a71-5d4e-4b9a-a1c6-2e7f90d4b5a3",
"appId": "1b6f4b1a-8f2f-4e3b-9c8b-9a2f6e4d7c11",
"displayName": "Contoso Payroll",
"type": 1,
"isManaged": true
},
"appType": 1,
"technicalOwners": {
"editCredentials": false,
"editOwners": false,
"editTechnicalOwners": false,
"editSettings": true,
"editBusinessOwners": false,
"extendActivity": true,
"editProperties": false
},
"businessOwners": {
"editBusinessOwners": false
},
"warnings": []
}

Example 2: Read the owner permissions using PowerShell​

This example reads the owner permissions with an app-only token. Before you run it, register an application and note its tenant ID, client ID and client secret.

$ErrorActionPreference = "Stop" # stop on a refused or failed request
$tenantId = "[TENANT_ID]"
$clientId = "[CLIENT_ID]"
$clientSecret = "[CLIENT_SECRET]" # read it from your secret store, never hard-code it
$scope = "[SCOPE]" # the .default scope from Create Application Registration
$uri = "[URI]" # the request URL above, with your Object ID and type

$token = Invoke-RestMethod -Method POST `
-Uri "https://login.microsoftonline.com/$tenantId/oauth2/v2.0/token" `
-ContentType "application/x-www-form-urlencoded" `
-Body @{ client_id = $clientId; client_secret = $clientSecret; grant_type = "client_credentials"; scope = $scope }

$headers = @{ "Authorization" = "Bearer $($token.access_token)" }

$permissions = Invoke-RestMethod -Method GET -Uri $uri -Headers $headers
$permissions.technicalOwners