Clarify public access requirement

Author: baanders

articles/digital-twins/concepts-azure-digital-twins-explorer.md

@@ -37,6 +37,8 @@ Developers may find this tool especially useful in the following scenarios:
 
 The explorer's main purpose is to help you visualize and understand your graph, and update your graph as needed. For large-scale solutions and for work that should be repeated or automated, consider using the [APIs and SDKs](./concepts-apis-sdks.md) to interact with your instance through code instead.
 
+[!INCLUDE [digital-twins-explorer-private-note.md](../../includes/digital-twins-explorer-private-note.md)]
+
 ## How to access
 
 The main way to access Azure Digital Twins Explorer is through the [Azure portal](https://portal.azure.com).

includes/digital-twins-access-explorer.md

@@ -19,5 +19,4 @@ Azure Digital Twins Explorer might automatically connect to your instance. If no
 
 If you see this box, enter *https://* into the field, followed by the host name of your instance (this can be found back on the instance's **Overview** page in the portal). These values together make up the instance URL. Select **Save** to connect to your instance.
 
->[!NOTE]
-> The hosted Azure Digital Twins Explorer can only access Azure Digital Twins instances with public access enabled. If you're using [Private Link](../articles/digital-twins/concepts-security.md#private-network-access-with-azure-private-link) to restrict access to your instance through a private endpoint, you can use Azure functions to deploy the Azure Digital Twins Explorer codebase privately in the cloud. For instructions on how to do this, see [Azure Digital Twins Explorer: Running in the cloud](https://github.com/Azure-Samples/digital-twins-explorer#running-in-the-cloud).
+[!INCLUDE [digital-twins-explorer-private-note.md](digital-twins-explorer-private-note.md)]

includes/digital-twins-explorer-private-note.md

@@ -0,0 +1,11 @@
+---
+author: baanders
+description: include file stating private endpoint limitation of Azure Digital Twins Explorer
+ms.service: digital-twins
+ms.topic: include
+ms.date: 04/19/2024
+ms.author: baanders
+---
+
+>[!IMPORTANT]
+> Azure Digital Twins Explorer **does not support** private endpoints. If you want to use Azure Digital Twins Explorer with an Azure Digital Twins instance that uses [Private Link](../articles/digital-twins/concepts-security.md#private-network-access-with-azure-private-link) to disable public access, you can deploy the Azure Digital Twins Explorer codebase privately in the cloud. For instructions on how to do this, see [Azure Digital Twins Explorer: Running in the cloud](https://github.com/Azure-Samples/digital-twins-explorer#running-in-the-cloud).