Skip to content

Commit 64e0f62

Browse files
committed
Merge branch 'patch-11' of github.com:shubhirajMsft/azure-docs-pr into shubhirajMsft/patch-11
2 parents e2ab55a + 7483ae9 commit 64e0f62

File tree

1 file changed

+16
-14
lines changed

1 file changed

+16
-14
lines changed

articles/machine-learning/concept-model-catalog.md

Lines changed: 16 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -157,20 +157,22 @@ Azure Machine Learning implements a default configuration of [Azure AI Content S
157157

158158
### Network isolation for models deployed via Serverless APIs
159159

160-
Endpoints for models deployed as Serverless APIs follow the public_network_access flag setting of the workspace in which the deployment exists. To secure your MaaS endpoint, disable the public_network_access flag on your workspace. Securing inbound communication from a client to your endpoint is possible by using a private endpoint for the workspace.
161-
162-
**Setting the public_network_access flag for the workspace:**
163-
* Go to the [Azure Portal](https://ms.portal.azure.com/)
164-
* Search for 'Azure Machine Learning', and choose your workspace
165-
* On the overview page, use the left navigation bar to go to Settings > Networking
166-
* Here under the Public Access tab you will have the option to set the Public Network Access flag settings
167-
* Save your changes (changes may take upto five minutes to propagate)
168-
169-
**Limitations:**
170-
* If you have a workspace with private endpoint created before July 11, new MaaS endpoints added to this workspace will not follow the networking configuration of the hub. New private endpoint and serverless API deployments need to be created.
171-
* If you have a workspace with MaaS deployments created before July 11 and you enable private endpoint on this workspace, the existing MaaS endpoints will not follow the workspace's networking configuration. New serverless API deployments need to be created.
172-
* Currently [On Your Data](#rag-with-models-deployed-as-serverless-apis) support is not available for MaaS deployments in private workspaces (public_network_access flag disabled).
173-
* Any network cofiguration change (eg. enabling or disabling the public_network_access flag) may take upto five minutes to propagate.
160+
Endpoints for models deployed as Serverless APIs follow the public network access (PNA) flag setting of the workspace in which the deployment exists. To secure your MaaS endpoint, disable the PNA flag on your workspace. You can secure inbound communication from a client to your endpoint by using a private endpoint for the workspace.
161+
162+
To set the PNA flag for the workspace:
163+
164+
* Go to the [Azure portal](https://ms.portal.azure.com/).
165+
* Search for _Azure Machine Learning_, and select your workspace from the list of workspaces.
166+
* On the Overview page, use the left navigation pane to go to **Settings** > **Networking**.
167+
* Under the **Public access** tab, you can configure settings for the public network access flag.
168+
* Save your changes. Your changes might take up to five minutes to propagate.
169+
170+
#### Limitations
171+
172+
* If you have a workspace with a private endpoint created before July 11, 2024, new MaaS endpoints added to this workspace won't follow its networking configuration. Instead, you need to create a new private endpoint for the workspace and create new serverless API deployments in the workspace so that the new deployments can follow the workspace's networking configuration.
173+
* If you have a workspace with MaaS deployments created before July 11, 2024, and you enable a private endpoint on this workspace, the existing MaaS deployments won't follow the workspace's networking configuration. For serverless API deployments in the workspace to follow the workspace's configuration, you need to create the deployments again.
174+
* Currently [On Your Data](#rag-with-models-deployed-through-maas) support isn't available for MaaS deployments in private workspaces, since private workspaces have the PNA flag disabled.
175+
* Any network configuration change (for example, enabling or disabling the PNA flag) might take up to five minutes to propagate.
174176

175177
## Learn more
176178

0 commit comments

Comments
 (0)