| title | titleSuffix | description | ms.service | author | ms.author | ms.topic | ms.date |
|---|---|---|---|---|---|---|---|
Troubleshoot failed service request: Error 404 (Sub-Domain not found) |
Azure Digital Twins |
Learn how to diagnose and resolve error 404 (Sub-Domain not found) status responses from Azure Digital Twins. |
digital-twins |
baanders |
baanders |
troubleshooting |
02/22/2022 |
This article describes causes and resolution steps for receiving a 404 error from service requests to Azure Digital Twins.
This error may occur when accessing an Azure Digital Twins instance using a service principal or user account that belongs to a different Azure Active Directory (Azure AD) tenant from the instance. The correct roles seem to be assigned to the identity, but API requests fail with an error status of 404 Sub-Domain not found.
Azure Digital Twins requires that all authenticating users belong to the same Azure AD tenant as the Azure Digital Twins instance.
[!INCLUDE digital-twins-tenant-limitation]
You can resolve this issue by having each federated identity from another tenant request a token from the Azure Digital Twins instance's "home" tenant.
[!INCLUDE digital-twins-tenant-solution-1]
If you're using the DefaultAzureCredential class in your code and you continue encountering this issue after getting a token, you can specify the home tenant in the DefaultAzureCredential options to clarify the tenant even when authentication defaults down to another type.
[!INCLUDE digital-twins-tenant-solution-2]
Read more about security and permissions on Azure Digital Twins: