Skip to content

Commit 756f78b

Browse files
committed
Fixing an SFI issue
1 parent 56ec4fb commit 756f78b

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/storage/blobs/data-lake-storage-access-control.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -332,10 +332,10 @@ A GUID is shown if the entry represents a user and that user doesn't exist in Mi
332332

333333
When you define ACLs for service principals, it's important to use the Object ID (OID) of the *service principal* for the app registration that you created. It's important to note that registered apps have a separate service principal in the specific Microsoft Entra tenant. Registered apps have an OID that's visible in the Azure portal, but the *service principal* has another (different) OID.
334334
Article
335-
To get the OID for the service principal that corresponds to an app registration, you can use the `az ad sp show` command. Specify the Application ID as the parameter. Here's an example of obtaining the OID for the service principal that corresponds to an app registration with App ID = ffffffff-eeee-dddd-cccc-bbbbbbbbbbb0. Run the following command in the Azure CLI:
335+
To get the OID for the service principal that corresponds to an app registration, you can use the `az ad sp show` command. Specify the Application ID as the parameter. Here's an example of obtaining the OID for the service principal that corresponds to an app registration with App ID = 00001111-aaaa-2222-bbbb-3333cccc4444. Run the following command in the Azure CLI:
336336

337337
```azurecli
338-
az ad sp show --id 18218b12-1895-43e9-ad80-6e8fc1ea88ce --query objectId
338+
az ad sp show --id 00001111-aaaa-2222-bbbb-3333cccc4444 --query objectId
339339
```
340340

341341
OID will be displayed.

0 commit comments

Comments
 (0)