Azure-docs: Azure Portal UI to assign roles to subnet is missing since 27.06.2019

[whut]

Actual

Yesterday, on 26.06.2019 I was able to open UI (separate blade for management of single subnet) with subnet details, where on Users tab I could add/remove role assignments to the subnet.

This is still documented in the Change subnet settings section of Add, change, or delete a virtual network subnet. Quote:

Users: You can control access to the subnet by using built-in roles or your own custom roles.

Today, on 27.06.2019, the blade for managing single subnet is missing. Instead a simple sidebar shows up, where there is no role management possible.

Expected

Bring back ability to view/edit subnet role assignments. Possibly via bringing back the subnet management UI, as it was available before and is still documented.

I know this may not be the right repo for reporting this issue, but could not found more appropriate one. This is an issue, not improvement, so feedback.azure.com is not the right place.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: b8332806-35c4-26e5-56e6-0286d728ad45
• Version Independent ID: ce76cee4-5629-7439-309c-9b9705891b57
• Content: Add, change, or delete an Azure virtual network subnet
• Content Source: articles/virtual-network/virtual-network-manage-subnet.md
• Service: virtual-network
• GitHub Login: @KumudD
• Microsoft Alias: kumud

[MohitVerma-MSFT]

@whut Thank you for your feedback! We will review and provide an update as appropriate.

[rdefreitas]

@MohitVerma-MSFT we've also come across the same issue. Our organization has built multiple workflows around this functionality and is critical to our security procedures. Please advise next steps.

[TravisCragg-MSFT]

@whut @rdefreitas I am following up with this, and will update as soon as I have any information.

[TravisCragg-MSFT]

@whut @rdefreitas we are working to get this functionality back to the portal, and apologize for any inconveniences that have happened!

[SattaRavi]

HI @TravisCragg-MSFT

Any ETA that you possibly can share? it would really help us set expectations.

[TravisCragg-MSFT]

@SattaRavi I am unable to give an ETA at this time, but this should be fixed in a timely manner.

If you need this blade immediately, you can use this preview portal link which will have the blade enabled.

[RZomerman]

in the meantime, you can also use the AZ commands to achieve the same (while they work on a fix):

Where $groupID is the objectID of the group or Service Principal (or user)
And $subscope is the ObjectId of the subnet itself as defined like:

$subscope = ‘/subscriptions/11111-1111-1111-1111-111111/resourceGroups/resgroup-001/providers/Microsoft.Network/virtualNetworks/vnet001/subnets/subnet002’

$groupID='11001-1010101-10100111-101010011'

New-AzRoleAssignment -ObjectId $groupid -RoleDefinitionName "Network Contributor" -Scope $subscope

[TravisCragg-MSFT]

@whut @rdefreitas @SattaRavi This has been fixed, and you should see the user management in the subnet blade.

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.