We will review this request.
This is a limitation in the Azure Portal for customers that are using v3 API. The portal is currently just using v2 API’s so there are a number of gaps and backward compatibility issues with regard to use of v3 APIs. We recommend just using the v3 capabilities via API for now. Work is underway to support v3 API’s in the portal. If UI tool is needed prior to this availability, the Azure Media Services Explorer tool (https://github.com/Azure/Azure-Media-Services-Explorer) can be used as it has full support for v3 API’s.Galdin Raphael commented
Looks like this is an issue only when using the v3 APIs. The portal behaves like it should when using the v2 APIs.Galdin Raphael shared this idea ·