Azure Media Indexer v2 automatically redacts certain content when generating transcripts, such as profanity. There is currently no way to turn off this content filtering, making the transcripts less useful.
Add a setting that allows this functionality to be toggled for each job2 votes
Why do you not support classic endpoints anymore?
I can imagine that media services were born to give streaming capabilities to big companies, but in my case I developed a CMS that is used by many companies, totally based on Azure (web app, storage, cdn, etc.). Sometimes I have designed for my customers a home page that has a video background. Obviously in this case I cannot ask to my customer to pay 50USD/month only for the video background.
For these basic cases the classic endpoint was very cheap and useful.
Obviously now I’m forced to switch to YouTube.1 vote
At present, it appears that you can create an AMS asset via ARM template and specify its storage account only. It would be great to also have the ability to configure media reserved units, streaming endpoints, and live streaming settings from a template as well.1 vote
Could you add a whitelist of websites that would only allow video to be streamed if your servers received the request from particular web pages, perhaps using the request "Referrer".
A sort of poor mans security over assets that you don't want other websites from having on there sites and using your data costs.0 votes
Currently we don’t support referrer blocking. However we support crossdomain.xml and clientaccesspolicy.xml to restrict domains. Also we will be adding CORS support. As an alternative you can also use Azure CDN rules and token feature for restriction.
- Don't see your idea?