Skip to content

Commit 557e21d

Browse files
DENKEN02MSFTDENKEN02MSFT
committed
Metadata and includes updated, minor Acrolinx fixes to improve score
1 parent 9b9fd40 commit 557e21d

File tree

4 files changed

+11
-11
lines changed

4 files changed

+11
-11
lines changed

‎articles/digital-twins/includes/digital-twins-tenant-limitation.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
22
author: baanders
3-
description: include file describing the cross-tenant limitation with Azure Digital Twins
3+
description: Include file describing the cross-tenant limitation with Azure Digital Twins.
44
ms.service: azure-digital-twins
55
ms.topic: include
6-
ms.date: 4/13/2021
6+
ms.date: 4/21/2025
77
ms.author: baanders
88
---
99

10-
As a result, requests to the Azure Digital Twins APIs require a user or service principal that is a part of the same tenant where the Azure Digital Twins instance resides. To prevent malicious scanning of Azure Digital Twins endpoints, requests with access tokens from outside the originating tenant will be returned a "404 Sub-Domain not found" error message. This error will be returned even if the user or service principal was given an Azure Digital Twins Data Owner or Azure Digital Twins Data Reader [role](../concepts-security.md) through [Microsoft Entra B2B](../../active-directory/external-identities/what-is-b2b.md) collaboration.
10+
As a result, requests to the Azure Digital Twins APIs require a user or service principal that is a part of the same tenant where the Azure Digital Twins instance resides. To prevent malicious scanning of Azure Digital Twins endpoints, requests with access tokens from outside the originating tenant return a "404 Sub-Domain not found" error message. This error is returned even if the user or service principal was given an Azure Digital Twins Data Owner or Azure Digital Twins Data Reader [role](../concepts-security.md) through [Microsoft Entra B2B](../../active-directory/external-identities/what-is-b2b.md) collaboration.

‎articles/digital-twins/includes/digital-twins-tenant-solution-1.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
---
22
author: baanders
3-
description: include file describing a token solution to the cross-tenant limitation with Azure Digital Twins
3+
description: Include file describing a token solution to the cross-tenant limitation with Azure Digital Twins.
44
ms.service: azure-digital-twins
55
ms.topic: include
6-
ms.date: 4/13/2021
6+
ms.date: 4/21/2025
77
ms.author: baanders
88
---
99

@@ -13,4 +13,4 @@ One way to do this is with the following CLI command, where `<home-tenant-ID>` i
1313
az account get-access-token --tenant <home-tenant-ID> --resource https://digitaltwins.azure.net
1414
```
1515

16-
After requesting this, the identity will receive a token issued for the `https://digitaltwins.azure.net` Microsoft Entra resource, which has a matching tenant ID claim to the Azure Digital Twins instance. Using this token in API requests or with your `Azure.Identity` code should allow the federated identity to access the Azure Digital Twins resource.
16+
After this request, the identity receives a token issued for the `https://digitaltwins.azure.net` Microsoft Entra resource, which has a matching tenant ID claim to the Azure Digital Twins instance. Using this token in API requests or with your `Azure.Identity` code should allow the federated identity to access the Azure Digital Twins resource.

‎articles/digital-twins/includes/digital-twins-tenant-solution-2.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
---
22
author: baanders
3-
description: include file describing a code solution to the cross-tenant limitation with Azure Digital Twins
3+
description: Include file describing a code solution to the cross-tenant limitation with Azure Digital Twins.
44
ms.service: azure-digital-twins
55
ms.topic: include
6-
ms.date: 12/07/2022
6+
ms.date: 4/21/2025
77
ms.author: baanders
88
---
99

‎articles/digital-twins/troubleshoot-error-404-digital-twins.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.service: azure-digital-twins
66
author: baanders
77
ms.author: baanders
88
ms.topic: troubleshooting
9-
ms.date: 09/06/2022
9+
ms.date: 4/21/2025
1010
---
1111

1212
# Troubleshoot Azure Digital Twins failed service request: Error 404 (Sub-Domain not found)
@@ -15,7 +15,7 @@ This article describes causes and resolution steps for receiving a 404 error fro
1515

1616
## Symptoms
1717

18-
This error may occur when accessing an Azure Digital Twins instance using a service principal or user account that belongs to a different [Microsoft Entra tenant](../active-directory/develop/quickstart-create-new-tenant.md) from the instance. The correct [roles](concepts-security.md) seem to be assigned to the identity, but API requests fail with an error status of `404 Sub-Domain not found`.
18+
This error might occur when accessing an Azure Digital Twins instance using a service principal or user account that belongs to a different [Microsoft Entra tenant](../active-directory/develop/quickstart-create-new-tenant.md) from the instance. The correct [roles](concepts-security.md) seem to be assigned to the identity, but API requests fail with an error status of `404 Sub-Domain not found`.
1919

2020
## Causes
2121

@@ -42,4 +42,4 @@ If you're using the `DefaultAzureCredential` class in your code and you continue
4242
## Next steps
4343

4444
Read more about security and permissions on Azure Digital Twins:
45-
* [Security for Azure Digital Twins solutions](concepts-security.md)
45+
* [Secure Azure Digital Twins](concepts-security.md)

0 commit comments

Comments
 (0)