@Vibu , Apologies for the delayed response from over the weekend. I'd been checking on this internally.
Using dashes in the file name for AMS Asset should be fine; Azure Media Service (AMS) has two main restrictions for the files name:
- The value of the name property cannot have any of the following percent-encoding-reserved characters: !*'();:@&=+$,/?%#[]". Also, there can only be one '.' for the file name extension.
- The length of the name should be at most 260 characters.
In addition to the general guidelines from Azure storage (blob name requirements and the NTFS name requirements)
Reference: Assets in Azure Media Services | Microsoft Learn
We did some tests by creating an asset with an mp4 file with a UUID name, and the stream is working successfully.
I suggest you do a simple test (steps below), and see how it goes.
- Rename the MP4 file to UUID name on local machine
- Create a new Asset and upload the UUID mp4 file
- Encode that Asset using any transform (to generate a streaming-ready Asset)
- Create a streaming locator, then test the streaming URL using any player or our media player demo page Azure Media Player (azureedge.net)
The streaming URL should be like this:
[Streaming Endpoint hostname]/[Streaming Locator ID]/{UUID}.ism/manifest