Hi @Phil
I hate to discourage customers from using features, but I would recommend that you try not to take a dependency right now on this feature for your use case scenario. Reason being is that we are re-evaluating this face redaction feature in light of current changes around Responsible AI.
We may be deprecating this feature in the very near future, and I would hate for you to get stuck on it.
See our recent announcement here -https://azure.microsoft.com/en-us/blog/responsible-ai-investments-and-safeguards-for-facial-recognition/
The specific section that is important for this feature is the following:
"new customers need to apply for access to use facial recognition operations in Azure Face API, Computer Vision, and Video Indexer. Existing customers have one year to apply and receive approval for continued access to the facial recognition services based on their provided use cases. By introducing Limited Access, we add an additional layer of scrutiny to the use and deployment of facial recognition to ensure use of these services aligns with Microsoft’s Responsible AI Standard and contributes to high-value end-user and societal benefit. This includes introducing use case and customer eligibility requirements to gain access to these services. Read about example use cases, and use cases to avoid, here."
For Azure Media Services, we are not planning to introduce new "gating" for responsible AI. We will be migrating some of our Face detection AI capabilities over to the Video Indexer service where we can consolidate all responsible AI development going forward with proper gating.
Hope that makes sense to you and feel free to ask questions.
As a solution for the short term, you may want to look into using an open source AI framework for the face detection, like NVidia or Intels AI offerings that can be integrated with GStreamer to manipulate video. I'm not sure if they have a specific redaction sample, but that would be a good place to build from.