-
Notifications
You must be signed in to change notification settings - Fork 230
Update boot-diagnostics.md #261
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
base: main
Are you sure you want to change the base?
Conversation
This update clarifies the prerequisites required when configuring Boot diagnostics to use a custom storage account instead of the default managed storage option.
Learn Build status updates of commit d914243:
|
File | Status | Preview URL | Details |
---|---|---|---|
articles/virtual-machines/boot-diagnostics.md | Details |
articles/virtual-machines/boot-diagnostics.md
- Line 64, Column 90: [Warning: hard-coded-locale - See documentation]
Link 'https://learn.microsoft.com/en-us/azure/role-based-access-control/built-in-roles/storage#storage-account-key-operator-service-role' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
- Line 64, Column 324: [Warning: hard-coded-locale - See documentation]
Link 'https://learn.microsoft.com/en-us/azure/role-based-access-control/custom-roles-portal' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
- Line 64, Column 90: [Suggestion: docs-link-absolute - See documentation]
Absolute link 'https://learn.microsoft.com/en-us/azure/role-based-access-control/built-in-roles/storage#storage-account-key-operator-service-role' will be broken in isolated environments. Replace with a relative link.
- Line 64, Column 324: [Suggestion: docs-link-absolute - See documentation]
Absolute link 'https://learn.microsoft.com/en-us/azure/role-based-access-control/custom-roles-portal' will be broken in isolated environments. Replace with a relative link.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
Use locale-neutral relative links for role-based access control references and custom role
Learn Build status updates of commit 8844019:
|
File | Status | Preview URL | Details |
---|---|---|---|
articles/virtual-machines/boot-diagnostics.md | Details |
articles/virtual-machines/boot-diagnostics.md
- Line 64, Column 291: [Warning: file-not-found - See documentation]
Invalid file link: 'articles/role-based-access-control/custom-roles-portal'.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
@microsoft-github-policy-service agree company="Microsoft" |
@eliaquimbrandao : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
small change for the locale-neutral relative links
Learn Build status updates of commit 5b88f41: ✅ Validation status: passed
For more details, please refer to the build report. |
Can you review the proposed changes? Note: Before we can merge, the image needs to be added to the repo. File names and references need to be changed to align with the MicrosoftDocs file naming standards. The standard includes using only numbers, lowercase letters, and hyphens in a file name (including extensions), and separating words and numbers with hyphens in file names. Example: AzurePortal1.png should be azure-portal-1.png. Also, the alt text for the image will need to be corrected. Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
This update clarifies the prerequisites required when configuring Boot diagnostics to use a custom storage account instead of the default managed storage option.
Purpose:
Helps customers avoid common permission issues when using a custom storage account for Boot diagnostics, reducing support requests and improving self-service troubleshooting.