Update how-to-manage-compute-instance.md #196
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updated document with below proposed changes:
Clarification about resource locations in the context of a workspace's resource group:
When resources such as Network Security Groups (NSGs), Public IPs, and Load Balancers are not in the same resource group as the Azure Machine Learning workspace, it's important to specify this in the documentation.
For example, if the VNET (Virtual Network) is located in a separate resource group for management purposes, customers should understand that these resources will be created in the same resource group as the VNET, not necessarily the workspace's resource group.
The documentation should explicitly note this distinction to avoid customers assuming that all resources are created in the workspace's resource group.
Expand resource lock behavior documentation for Compute Instances:
Resource locks can affect creation of a Compute Instance, not just resizing.
The documentation should include this information and explicitly state that locks can prevent both the creation and resizing of Compute Instances.
This clarification will help ensure customers are aware of potential issues caused by resource locks during either operation.