We are working on a strategy to move from on-premises AD RMS to Azure IP; however, we have encountered a blocker in our migration strategy: Azure IP cannot authenticate a user not located in an Azure AD tenant. In this scenario, we have implemented AD RMS in a resource forest and account forest scenario. The resource forest contains AD RMS, the protected content, AD FS, and contact objects of the users in the account forest. The account forest contains the user objects and uses Ping to federate with the resource forest. These user accounts can use any email address suffix to register for an ID. They are hosted in the account forest AD, but could map to an email address @gmail or @contoso, etc. What we are proposing is that resource forest utilize Azure IP to protect content for the users in the account forest. However, we cannot authenticate these users. We have, internally, evaluated/tested the following different strategies without success:

-Federating the Azure AD tenant with an on-premises AD partner (preferred). This is not currently supported.
-Synchronize contact objects from the resource forest to Azure AD (or create net new contact objects in AAD). The result is that Azure IP cannot use a contact object to authenticate the user.
-Create New Guest User accounts in the resource AAD tenant. The result is that Azure IP cannot use a guest user to authenticate the user.
-Use social identities with Azure IP: Azure IP does not currently support social identities. This is also the reason we cannot synchronize user accounts from the account forest to a corresponding account tenant.

Microsoft Azure, the cloud platform, has recently taken a few main steps as a media offerings issuer. The platform proved its potential to address high volumes of labor when it performed the report streaming of Rio Olympics 2016. On September 12, 2016, the Microsoft Azure Media services crew announced its choice to end up a part of the upcoming IBC Hackfest.

The bulletins made by the Azure Media services were as follows:

Multi-DRM:

Azure just recently announced that it'd also be imparting the Apple Fairplay Streaming DRM service. With this, Azure Media offerings will now offer services for all principal DRMs i.e. Apple Fairplay, Microsoft PlayReady, and Google Widevine. this can help the media customers in presenting premium content that is DRM protected to a extensive range of target market. Azure now also gives dynamic encryption on their streaming server. this is used to encrypt media on-the-fly, some thing this is vital for live streaming and video-on-demand (VOD). With those more suitable content protection services, Azure will now allow you to develop a multi-DRM solution fast and reliably.

Media Analytics:

The group additionally introduced Azure Media Analytics that may be a series of vision and speech offerings consisting of movement Detection, Hyper-lapse, content Moderation, Optical man or woman reputation (OCR), Video Summarization, and Face Detection. Azure Media Redactor will also be added to the offerings, with the intention to be very useful in news media situations and public safety because it will perform anonymization through face blurring services.

HEVC:

The Azure Media services team is currently trying out out its HEVC encoding offerings with its clients. the brand new encoder has been evolved at the equal platform that the top class Encoder. It presents enhancements which encompass support for HDR content and 4K decision encoding. https://goo.gl/FNhVHm

Azure Portal will now feature Azure Media services:

Azure Media offerings will now be usually to be had within the Azure portal. There were some additions inside the functions of the portal as nicely. these include FairPlay DRM help, closed caption configurations, and improved stay streaming workflow. whilst you won’t be capable of create a new account inside the vintage portal, you can nevertheless access it and manage your existing account through pingingmanage.windowsazure.com. whilst you could nonetheless access Azure’s vintage portal, it's miles in all likelihood to be terminated quickly. this is why it's far cautioned that customers switch over to the brand new portal as soon as possible.

Azure Cool garage:

The Azure team has announced that the Azure Cool garage will now be supported in media workflows. Now, customers can certainly upload their mezzanines to Azure Cool garage. The benefit of this is that it's far a whole lot greater within your budget than different options for garage. every time you need to get admission to the facts at the Azure Cool storage, you can definitely transcode and put together it for use with the lively garage i.e. warm storage.

With these trendy announcements via the Azure Media services, Microsoft Azure is without a doubt trying to target corporations that are searching out hosts for his or her streamed occasions up ahead.

Currently Depp Inspection is an all-or-nothing setting.

It would be highly useful if there was a level of customization - either as a 'Only Selected Groups/Users', or a setting to override Local Agents where the online service would happily process the additional info.

Specifically, we have found the product causes a few sites to not work as expected. And installer doesn't always place the custom Root CA in each workstation's Trusted Root Authority store - something we are working on. So it makes it very difficult to test the functionality by including or excluding users via GPO, AD Groups, etc.

Having some flexibility would allow us to test and push the product with more confidence.