You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/ai-studio/how-to/create-projects.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -126,7 +126,7 @@ In addition, a number of resources are only accessible by users in your project
126
126
| workspacefilestore | {project-GUID}-code | Hosts files created on your compute and using prompt flow |
127
127
128
128
> [!NOTE]
129
-
> Storage connections are not created directly with the project when your storage account has public network access set to disabled. These are created instead when a first user accesses AI Studio over a private network connection. [Troubleshoot storage connections](troubleshoot-secure-connection-project.md#troubleshoot-missing-storage-connections)
129
+
> Storage connections are not created directly with the project when your storage account has public network access set to disabled. These are created instead when a first user accesses AI Studio over a private network connection. [Troubleshoot storage connections](troubleshoot-secure-connection-project.md#troubleshoot-configurations-on-connecting-to-storage)
Copy file name to clipboardExpand all lines: articles/ai-studio/how-to/troubleshoot-secure-connection-project.md
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -123,13 +123,14 @@ If you use a proxy, it may prevent communication with a secured project. To test
123
123
* Configure your proxy server to forward DNS requests to Azure DNS.
124
124
* Ensure that the proxy allows connections to AML APIs, such as "*.\<region\>.api.azureml.ms" and "*.instances.azureml.ms"
125
125
126
-
## Troubleshoot missing storage connections
126
+
## Troubleshoot configurations on connecting to storage
127
127
128
128
When you create a project, a number of connections to Azure storage are auto-created for data upload scenarios and artifact storage including prompt flow. When your hub's associated Azure Storage account is having public network access set to 'Disabled', there may be a delay in these storage connections to be created.
129
129
130
130
Try the following steps to troubleshoot:
131
-
132
131
1. In Azure Portal, check the network settings of the storage account that is associated to your hub.
133
-
1. Review your internet connection, and make sure you are using a private connection that is allowed by your storage account.
134
-
1. Navigate to AI Studio > your project > project settings.
135
-
1. Refresh the page. A number of connections should be created including 'workspaceblobstore'.
132
+
* If public network access is set to __Enabled from selected virtual networks and IP addresses__, ensure the correct IP address ranges are added to access your storage account.
133
+
* If public network access is set to __Disabled__, ensure you have a private endpoint configured from your Azure virtual network to your storage account with Target sub-resource as blob. In addition, you must grant the [Reader](/azure/role-based-access-control/built-in-roles#reader) role for the storage account private endpoint to the managed identity.
134
+
2. In Azure Portal, navigate to your AI Studio hub. Ensure the managed virtual network is provisioned and the outbound private endpoint to blob storage is Active. For more on provisioning the managed virtual network, see [How to configure a managed network for Azure AI Studio hubs](configure-managed-network.md).
135
+
3. Navigate to AI Studio > your project > project settings.
136
+
4. Refresh the page. A number of connections should be created including 'workspaceblobstore'.
0 commit comments