Skip to content

Commit 9ea5a93

Browse files
Merge pull request #234849 from ermereen/patch-2
Update to reflect AAS managed identities support
2 parents 1bd97aa + 5f21401 commit 9ea5a93

File tree

1 file changed

+1
-15
lines changed

1 file changed

+1
-15
lines changed

articles/analysis-services/analysis-services-addservprinc-admins.md

Lines changed: 1 addition & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -95,21 +95,7 @@ The following Resource Manager template deploys an Analysis Services server with
9595

9696
## Using managed identities
9797

98-
A managed identity can also be added to the Analysis Services Admins list. For example, you might have a [Logic App with a system-assigned managed identity](../logic-apps/create-managed-service-identity.md), and want to grant it the ability to administer your server.
99-
100-
In most parts of the Azure portal and APIs, managed identities are identified using their service principal object ID. However, Analysis Services requires that they be identified using their client ID. To obtain the client ID for a service principal, you can use the Azure CLI:
101-
102-
```azurecli
103-
az ad sp show --id <ManagedIdentityServicePrincipalObjectId> --query appId -o tsv
104-
```
105-
106-
Alternatively you can use PowerShell:
107-
108-
```powershell
109-
(Get-AzureADServicePrincipal -ObjectId <ManagedIdentityServicePrincipalObjectId>).AppId
110-
```
111-
112-
You can then use this client ID in conjunction with the tenant ID to add the managed identity to the Analysis Services Admins list, as described above.
98+
Managed identies that are added to database or server roles will be unable to login to the service or do any operations. Managed identities for service principals are not supported in Azure Analysis Services.
11399

114100
## Related information
115101

0 commit comments

Comments
 (0)