Proper messaging required for AFEC “Features” that require “ManualApprove”.

Some subscription level features like “Microsoft.Network/AllowInternalDelegations” requires manual approval from Azure backend.

User registers for the feature at their end using “Register-AzProviderFeature” and then does a “Get-AzProviderFeature” to know the “RegistrationState”.

Now for features that require manual approval from Azure backend, these features will show up as “Pending” in the “RegistrationState”.

Customers continue to run “Get-AzProviderFeature” hoping that “RegistrationState” will change from “Pending” to “Registered” soon, but this never happens until and unless some from Microsoft approves the feature.

This further gives an impression to user that their registration is stuck in “Pending” state and they continue to wait and finally give up and raise a support request.

Expectation is , we should be very clear in the output of “Get/Register-AzProviderFeature” that customer part is done and now they need to raise a support request with Microsoft so that Microsoft can approve the pending request for them. This in-turn will change the “RegistrationState” state from “Pending” to “Registered”

Example :-

Register-AzProviderFeature -FeatureName "AllowInternalDelegations" -ProviderNamespace "Microsoft.Network"

FeatureName ProviderName RegistrationState
----------- ------------ -----------------
AllowInternalDelegations Microsoft.Network Pending

Get-AzProviderFeature -FeatureName "AllowInternalDelegations" -ProviderNamespace "Microsoft.Network"

FeatureName ProviderName RegistrationState
----------- ------------ -----------------
AllowInternalDelegations Microsoft.Network Pending

How about “RegistrationState” output be something like :- “Pending – Waiting Microsoft Approval – Please raise a support Ticket for approval”

Please Note :- Above change should only be applicable to Features that require “Manual” approval from backend and not for features that are set to “AutoApprove”.

Or if PowerShell team is not the right team, can you please route it to appropriate team for further triage please. Same should be applicable to CLI as well.

Start with the Register-AzProviderFeature and Get-AzProviderFeature entry points and trace how RegistrationState is displayed for Microsoft.Network features. Check how Manual approval is distinguished from AutoApprove, then add or update coverage for the Pending output so manual-approval features direct users to raise a Microsoft support request while automatic features retain their existing behavior.

Written by the indexing model from the issue text.