-
Notifications
You must be signed in to change notification settings - Fork 126
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
Adding explicitly requirement to set context of subscription #95
Conversation
If we can update this document explicitly defining that subscription for each context should be set in a certain way then it might help in future to have less problems. Had a ticket with Support team and even they couldn't tell me immediately what's the problem. And the problem was that I set context as az cli way and was registering feature via azure powershell and there was no error or hint to tell me that I'm enabling feature for wrong subscription. Ticket is RE: Cant create vm encryption at host - TrackingID#2411200050000262
@GomanovNA : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
Learn Build status updates of commit 47b7475: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
@roygara Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@GomanovNA Thanks for helping to improve our docs, we appreciate it! Overall this looks good, just two changes then it's good to go. :)
articles/virtual-machines/disks-enable-host-based-encryption-portal.md
Outdated
Show resolved
Hide resolved
articles/virtual-machines/disks-enable-host-based-encryption-portal.md
Outdated
Show resolved
Hide resolved
Co-authored-by: rogara <[email protected]>
Learn Build status updates of commit 7cd47b7: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
@roygara, For convenience, I committed your suggestions and merged this PR based on your approval. If this article requires further changes, please open a separate pull request. Thanks! |
If we can update this document explicitly defining that subscription for each context should be set in a certain way then it might help in future to have less problems. Had a ticket with Support team and even they couldn't tell me immediately what's the problem. And the problem was that I set context as az cli way and was registering feature via azure powershell and there was no error or hint to tell me that I'm enabling feature for wrong subscription. Ticket is RE: Cant create vm encryption at host - TrackingID#2411200050000262