Skip to content

Commit e1b2971

Browse files
committed
Integrate limitation into page
1 parent 929389a commit e1b2971

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

articles/digital-twins/how-to-enable-private-link.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -244,9 +244,11 @@ For a sample template that allows an Azure function to connect to Azure Digital
244244

245245
This template creates an Azure Digital Twins instance, a virtual network, an Azure function connected to the virtual network, and a Private Link connection to make the Azure Digital Twins instance accessible to the Azure function through a private endpoint.
246246

247-
## Troubleshoot
247+
## Limitations and troubleshooting
248248

249-
Here are some common issues that might arise when using Private Link with Azure Digital Twins.
249+
A limitation of using Private Link with Azure Digital Twins is that cross-tenant scenarios are not supported.
250+
251+
For troubleshooting, here are some common issues that might arise:
250252

251253
* **Issue:** When trying to access Azure Digital Twins APIs, you see an HTTP error code 403 with the following error in the response body:
252254
```json
@@ -266,9 +268,6 @@ Here are some common issues that might arise when using Private Link with Azure
266268

267269
For more Private Link troubleshooting suggestions, see [Troubleshoot Azure Private Endpoint connectivity problems](../private-link/troubleshoot-private-endpoint-connectivity.md).
268270

269-
## Limitation:
270-
Cross-tenant scenarios are not supported by Azure Digital Twins.
271-
272271
## Next steps
273272

274273
Quickly set up a protected environment with Private Link using an ARM template: [Azure Digital Twins with Azure function and Private Link](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.digitaltwins/digitaltwins-with-function-private-link).

0 commit comments

Comments
 (0)