The fate of the Azure Resource Explorer

%3CLINGO-SUB%20id%3D%22lingo-sub-2817336%22%20slang%3D%22en-US%22%3EThe%20fate%20of%20the%20Azure%20Resource%20Explorer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2817336%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20Azure%20Resource%20Explorer%20on%20portal(1)%20still%20being%20developed%20by%20Microsoft%3F%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fportal.azure.com%2F%23blade%2FHubsExtension%2FArmExplorerBlade%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fportal.azure.com%2F%23blade%2FHubsExtension%2FArmExplorerBlade%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EE.g.%20API%20version%20used%20for%26nbsp%3BMicrosoft.Network%2FvirtualNetworks%20does%20not%20list%20VNet%20peers%20and%20VNet%20peering%20resources%20are%20not%20visible%20on%20tool%20at%20all.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20anyone%20actively%20maintaining%20this%3F%3C%2FP%3E%3CP%3EIs%20this%20going%20to%20be%20replaced%20with%20something%20else%3F%20(%3CA%20href%3D%22https%3A%2F%2Fresources.azure.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fresources.azure.com%3C%2FA%3E)%3C%2FP%3E%3CP%3EHas%20there%20been%20any%20work%20to%20replace%20manual%20swagger%20updates%20with%20the%20automatic%20process%3F%3C%2FP%3E%3CP%3EIs%20there%20PO%2FPM%20who%20should%20re-evaluate%20if%20the%20tool%20is%20suitable%20for%20production%20usage%20or%20not%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECurrently%20aging%20of%20the%20API%20versions%20and%20other%20limitations%20really%20limits%20usability%20of%20the%20tool%20and%20to%20get%20proper%20information%20users%20needs%20to%20use%20e.g.%20CLI%20tools%20to%20fetch%20data%20from%20API%20or%20alternatively%20use%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fresources.azure.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fresources.azure.com%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Senior Member

Is Azure Resource Explorer on portal(1) still being developed by Microsoft?

https://portal.azure.com/#blade/HubsExtension/ArmExplorerBlade

 

E.g. API version used for Microsoft.Network/virtualNetworks does not list VNet peers and VNet peering resources are not visible on tool at all.

 

Is anyone actively maintaining this?

Is this going to be replaced with something else? (https://resources.azure.com)

Has there been any work to replace manual swagger updates with the automatic process?

Is there PO/PM who should re-evaluate if the tool is suitable for production usage or not?

 

Currently aging of the API versions and other limitations really limits usability of the tool and to get proper information users needs to use e.g. CLI tools to fetch data from API or alternatively use https://resources.azure.com

0 Replies