Add Microsoft.Compute entry to subscription setup#4369
Conversation
Added Microsoft.Compute entry with VM resources link. Hit a snag when I was trying to set this up, needed to have the Microsoft compute resource rp added to your subscription in order to get the ssh key download in step 3 when you provision the VM. I have added that piece to the instructions in hope others don't have the same issue.
|
@Bob-Pratt : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
@Bob-Pratt : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 3a9b622:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| azure-local/small-form-factor/small-form-factor-subscription-setup.md | Details |
azure-local/small-form-factor/small-form-factor-subscription-setup.md
- Line 37, Column 41: [Warning: hard-coded-locale - See documentation]
Link 'https://learn.microsoft.com/en-us/azure/templates/microsoft.compute/virtualmachines?pivots=deployment-language-bicep' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. - Line 37, Column 41: [Suggestion: docs-link-absolute - See documentation]
Absolute link 'https://learn.microsoft.com/en-us/azure/templates/microsoft.compute/virtualmachines?pivots=deployment-language-bicep' 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.
|
Learn Build status updates of commit 8a4923f: 💡 Validation status: suggestions
azure-local/small-form-factor/small-form-factor-subscription-setup.md
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. |
Bob-Pratt
left a comment
Bob-Pratt
left a comment
There was a problem hiding this comment.
fixed the warning I got from the pull request, amnd removed the en-us from the link. Many apologies I am fairly noob when it comes to github
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
Bot
added
the
aq-pr-triaged
There was a problem hiding this comment.
Pull request overview
Updates the Azure Local small form factor subscription setup documentation to prevent VM provisioning issues by ensuring the required Azure Resource Provider is registered.
Changes:
- Adds
Microsoft.Computeto the list of required registered resource providers, with a link to VM resources. - Fixes formatting of the “Next steps” bullet so it renders correctly.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| | `Microsoft.Edge` | All use cases | [Site, site configuration](/azure/templates/microsoft.edge/sites?pivots=deployment-language-bicep) | | ||
| | `Microsoft.AzureStackHCI` | All use cases | [Edge machine (also known as provisioned machine)](/azure/templates/microsoft.azurestackhci/edgemachines?pivots=deployment-language-bicep) | | ||
| | `Microsoft.HybridCompute` | All use cases | [Arc-connected machines in the managed resource group](/azure/templates/microsoft.hybridcompute/machines?pivots=deployment-language-bicep) | | ||
| | `Microsoft.Compute` | All use cases | [VM resources](https://learn.microsoft.com/azure/templates/microsoft.compute/virtualmachines?pivots=deployment-language-bicep) | |
Added Microsoft.Compute entry with VM resources link.
Hit a snag when I was trying to set this up, needed to have the Microsoft compute resource rp added to your subscription in order to get the ssh key download in step 3 when you provision the VM. I have added that piece to the instructions in hope others don't have the same issue.