Skip to content

Commit 38f7a7b

Browse files
authored
Merge pull request #210300 from baanders/9-6-titles
ADT: Clarify ADT-specific articles
2 parents 7cf0d4e + e33274c commit 38f7a7b

37 files changed

+72
-57
lines changed

articles/digital-twins/.openpublishing.redirection.digital-twins.json

Lines changed: 16 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -144,7 +144,12 @@
144144
},
145145
{
146146
"source_path": "how-to-configure-postman.md",
147-
"redirect_url": "/azure/digital-twins/how-to-use-postman",
147+
"redirect_url": "/azure/digital-twins/how-to-use-postman-with-digital-twins",
148+
"redirect_document_id": false
149+
},
150+
{
151+
"source_path": "how-to-use-postman.md",
152+
"redirect_url": "/azure/digital-twins/how-to-use-postman-with-digital-twins",
148153
"redirect_document_id": true
149154
},
150155
{
@@ -202,6 +207,16 @@
202207
"redirect_url": "/azure/digital-twins/how-to-manage-routes",
203208
"redirect_document_id": false
204209
},
210+
{
211+
"source_path": "troubleshoot-error-403.md",
212+
"redirect_url": "/azure/digital-twins/troubleshoot-error-403-digital-twins",
213+
"redirect_document_id": true
214+
},
215+
{
216+
"source_path": "troubleshoot-error-404.md",
217+
"redirect_url": "/azure/digital-twins/troubleshoot-error-404-digital-twins",
218+
"redirect_document_id": true
219+
},
205220
{
206221
"source_path": "how-to-multitenant-applications.md",
207222
"redirect_url": "/previous-versions/azure/digital-twins/how-to-multitenant-applications",

articles/digital-twins/TOC.yml

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -103,8 +103,8 @@
103103
href: how-to-query-graph.md
104104
- name: Develop client apps
105105
items:
106-
- name: Make API requests with Postman
107-
href: how-to-use-postman.md
106+
- name: Call Azure Digital Twins APIs with Postman
107+
href: how-to-use-postman-with-digital-twins.md
108108
- name: Use 3D Scenes Studio
109109
href: how-to-use-3d-scenes-studio.md
110110
- name: Write app authentication code
@@ -149,12 +149,12 @@
149149
href: troubleshoot-performance.md
150150
- name: Known issues
151151
href: troubleshoot-known-issues.md
152-
- name: Problem resolution
152+
- name: Problem resolution in Azure Digital Twins
153153
items:
154154
- name: Error 403 (Forbidden)
155-
href: troubleshoot-error-403.md
155+
href: troubleshoot-error-403-digital-twins.md
156156
- name: Error 404 (Sub-Domain not found)
157-
href: troubleshoot-error-404.md
157+
href: troubleshoot-error-404-digital-twins.md
158158
- name: Azure Digital Twins Explorer authentication error
159159
href: troubleshoot-error-azure-digital-twins-explorer-authentication.md
160160
- name: CLI parsing failures

articles/digital-twins/concepts-apis-sdks.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ ms.service: digital-twins
1717

1818
# Azure Digital Twins APIs and SDKs
1919

20-
This article gives an overview of the Azure Digital Twins APIs available, and the methods for interacting with them. You can either use the REST APIs directly with their associated Swaggers (through a tool like [Postman](how-to-use-postman.md)), or through an SDK.
20+
This article gives an overview of the Azure Digital Twins APIs available, and the methods for interacting with them. You can either use the REST APIs directly with their associated Swaggers (through a tool like [Postman](how-to-use-postman-with-digital-twins.md)), or through an SDK.
2121

2222
Azure Digital Twins comes equipped with control plane APIs, data plane APIs, and SDKs for managing your instance and its elements.
2323
* The control plane APIs are [Azure Resource Manager (ARM)](../azure-resource-manager/management/overview.md) APIs, and cover resource management operations like creating and deleting your instance.
@@ -101,7 +101,7 @@ The available helper classes are:
101101
102102
The following list provides more detail and general guidelines for using the APIs and SDKs.
103103

104-
* You can use an HTTP REST-testing tool like Postman to make direct calls to the Azure Digital Twins APIs. For more information about this process, see [Make API requests with Postman](how-to-use-postman.md).
104+
* You can use an HTTP REST-testing tool like Postman to make direct calls to the Azure Digital Twins APIs. For more information about this process, see [Call the Azure Digital Twins APIs with Postman](how-to-use-postman-with-digital-twins.md).
105105
* To use the SDK, instantiate the `DigitalTwinsClient` class. The constructor requires credentials that can be obtained with different kinds of authentication methods in the `Azure.Identity` package. For more on `Azure.Identity`, see its [namespace documentation](/dotnet/api/azure.identity?view=azure-dotnet&preserve-view=true).
106106
* You may find the `InteractiveBrowserCredential` useful while getting started, but there are several other options, including credentials for [managed identity](/dotnet/api/azure.identity.interactivebrowsercredential?view=azure-dotnet&preserve-view=true), which you'll likely use to authenticate [Azure functions set up with MSI](../app-service/overview-managed-identity.md?tabs=dotnet) against Azure Digital Twins. For more about `InteractiveBrowserCredential`, see its [class documentation](/dotnet/api/azure.identity.interactivebrowsercredential?view=azure-dotnet&preserve-view=true).
107107
* Requests to the Azure Digital Twins APIs require a user or service principal that is a part of the same [Azure Active Directory](../active-directory/fundamentals/active-directory-whatis.md) (Azure AD) tenant where the Azure Digital Twins instance exists. 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 through [Azure AD B2B](../active-directory/external-identities/what-is-b2b.md) collaboration. For information on how to achieve access across multiple tenants, see [Write app authentication code](how-to-authenticate-client.md#authenticate-across-tenants).
@@ -128,8 +128,8 @@ From here, you can view the metrics for your instance and create custom views.
128128

129129
## Next steps
130130

131-
See how to make direct requests to the APIs using Postman:
132-
* [Make API requests with Postman](how-to-use-postman.md)
131+
See how to make direct requests to the Azure Digital Twins APIs using Postman:
132+
* [Call the Azure Digital Twins APIs with Postman](how-to-use-postman-with-digital-twins.md)
133133

134134
Or, practice using the .NET SDK by creating a client app with this tutorial:
135135
* [Code a client app](tutorial-code.md)

articles/digital-twins/concepts-security.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -85,7 +85,7 @@ The following list describes the levels at which you can scope access to Azure D
8585

8686
### Troubleshoot permissions
8787

88-
If a user attempts to perform an action not allowed by their role, they may receive an error from the service request reading `403 (Forbidden)`. For more information and troubleshooting steps, see [Troubleshoot failed service request: Error 403 (Forbidden)](troubleshoot-error-403.md).
88+
If a user attempts to perform an action not allowed by their role, they may receive an error from the service request reading `403 (Forbidden)`. For more information and troubleshooting steps, see [Troubleshoot Azure Digital Twins failed service request: Error 403 (Forbidden)](troubleshoot-error-403-digital-twins.md).
8989

9090
## Managed identity for accessing other resources
9191

articles/digital-twins/how-to-send-twin-to-twin-events.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -85,7 +85,7 @@ Now, your function can receive events through your Event Grid topic. The data fl
8585

8686
The last step is to verify that the flow is working, by updating a twin and checking that related twins are updated according to the logic in your Azure function.
8787

88-
To kick off the process, update the twin that's the source of the event flow. You can use the [Azure CLI](/cli/azure/dt/twin#az-dt-twin-update), [Azure Digital Twins SDK](how-to-manage-twin.md#update-a-digital-twin), or [Azure Digital Twins REST APIs](how-to-use-postman.md?tabs=data-plane) to make the update.
88+
To kick off the process, update the twin that's the source of the event flow. You can use the [Azure CLI](/cli/azure/dt/twin#az-dt-twin-update), [Azure Digital Twins SDK](how-to-manage-twin.md#update-a-digital-twin), or [Azure Digital Twins REST APIs](how-to-use-postman-with-digital-twins.md?tabs=data-plane) to make the update.
8989

9090
Next, query your Azure Digital Twins instance for the related twin. You can use the [Azure CLI](/cli/azure/dt/twin#az-dt-twin-query), or the [Azure Digital Twins REST APIs and SDK](how-to-query-graph.md#run-queries-with-the-api). Verify that the twin received the data and updated as expected.
9191

0 commit comments

Comments
 (0)