@Jeff Thanks for reaching out to Microsoft Q&A, apologize for any inconvenience caused on this.
I have tried creating a streaming locator in one of the existing media services in our subscription. I am able to create it successfully without any issues.
As you are facing the issue while creating the streaming locator can you try creating it through this CLI cmdlet az ams streaming-locator create.
az ams streaming-locator create --account-name
--asset-name
--name
--resource-group
--streaming-policy-name
[--alternative-media-id]
[--content-key-policy-name]
[--content-keys]
[--end-time]
[--filters]
[--start-time]
[--streaming-locator-id]
If you still facing the issue, could you please help us more information to check and assist you further.
- If you are creating streaming locator through portal, please do share the portal sessionId (using keyboards keys ctrl+alt+d), operation Id or correlation Id, media service resource name and timestamp (utc).