Update note on subnet delegation requirements #127544
Conversation
Because the Microsoft.Web/serverFarms resource provider shows on the portal even if the service is not registered for the subscription, it might become difficult to troubleshoot. The error message when it is not registered says the setup was not able to set the delegation, instead of saying the resource is not registered. Most of my customers assume it is a permission issue, not a service registration issue.
|
@ArmandoLacerda : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
There was a problem hiding this comment.
Pull Request Overview
Updates documentation to clarify subnet delegation requirements for API Management VNet outbound integration. The change addresses a common troubleshooting confusion where users see the Microsoft.Web/serverFarms resource provider in the portal but encounter delegation errors when the service isn't properly registered.
- Clarifies that the Microsoft.Web/serverFarms resource provider must be registered even if visible in the portal
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
| @@ -62,7 +62,7 @@ The subnet needs to be delegated to the **Microsoft.Web/serverFarms** service. | |||
|
|
|||
|
|
|||
| > [!NOTE] | |||
| > You might need to register the `Microsoft.Web/serverFarms` resource provider in the subscription so that you can delegate the subnet to the service. | |||
| > You might need to register the `Microsoft.Web/serverFarms` resource provider in the subscription so that you can delegate the subnet to the service, even if you see it on the list of available services in the subnet delegation setup in the portal. | |||
There was a problem hiding this comment.
[nitpick] The sentence structure could be improved for clarity. Consider: 'You might need to register the Microsoft.Web/serverFarms resource provider in the subscription to delegate the subnet to the service, even if you see it listed as an available service in the portal's subnet delegation setup.'
| > You might need to register the `Microsoft.Web/serverFarms` resource provider in the subscription so that you can delegate the subnet to the service, even if you see it on the list of available services in the subnet delegation setup in the portal. | |
| > You might need to register the `Microsoft.Web/serverFarms` resource provider in the subscription to delegate the subnet to the service, even if you see it listed as an available service in the portal's subnet delegation setup. |
Copilot uses AI. Check for mistakes.
|
Learn Build status updates of commit 2e19ffb: ✅ Validation status: passed
For more details, please refer to the build report. |
|
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
Because the Microsoft.Web/serverFarms resource provider shows on the portal even if the service is not registered for the subscription, it might become difficult to troubleshoot. The error message when it is not registered says the setup was not able to set the delegation, instead of saying the resource is not registered. Most of my customers assume it is a permission issue, not a service registration issue.