Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update how-to-manage-compute-instance.md #196

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

bhgtankita
Copy link

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.

Copy link
Contributor

@bhgtankita : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Copy link
Contributor

Learn Build status updates of commit db1882e:

✅ Validation status: passed

File Status Preview URL Details
articles/machine-learning/how-to-manage-compute-instance.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@v-dirichards
Copy link
Contributor

@sdgilley

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged C+L Pull Request Review Team label label Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants