Webinar:Monitoring changes and access events in AD and Azure AD

11/17/2016 11:00:00 AM [(UTC-05:00) Eastern Time (US & Canada)]

Knowing what’s happening in Active Directory has always been critical. That was increasingly true as more and more applications inside your network came to rely on AD for identity, authentication and authorization.
But now Active Directory is connected to and/or even itself exists in the cloud. Anyone using an Azure service or Office 365 is already using Azure Active Directory whether they realize it or not. Most of us do realize it and therefore we have connected our on-premise AD with Azure AD using synchronization (think Azure AD Connect and before that dirsync) and in some cases with Federation (think ADFS, et al).

Is Azure AD simply a projection of on-premise Active Directory? And therefore not in need of monitoring? Not so fast. Azure AD isn’t simply a read-only projection of your on-premise AD. Users accounts and groups can be created directly in Azure AD with no relationship to on-premise AD objects. There are situations where you must do that and of course non-compliant admins or intruders will certainly do that for a variety of reasons. Whether intentional or not you need to know when objects are created or changed directly in Azure AD that don’t correspond to on-premise AD objects.

Read more at – Webinar:Monitoring changes and access events in AD and Azure AD