Let’s take a look at how admins can manage MFA configurations in Azure AD.

As Microsoft keeps improving MFA standards, it is essential for admins to keep track of users who registered for MFA, who is not registered for MFA, and who enabled MFA for a specific user in the organization. For a secure experience, it is important to verify whether all users in the organization comply with the MFA configuration. MFA has the advantage of requiring additional verification methods other than the username and password when logging in to the Microsoft portal.

They can be used to audit who did what given a specific resource.In today’s world, everyone in the organization prefers using Multi-factor Authentication (MFA) as an extra level of security beyond traditional credentials. Summarized you can say that the Activity Log and Resource Log contain many logs and a subset of those are audit logs. For example, an Azure Data Lake Analytics resource has a specific 'Audit' log category. Some resources have dedicated log categories for the resource log that indicates entries that are interesting from an auditing perspective. Parts of the activity log, the resource log and the azure AD log kind are audit logs. There's a single activity log for each Azure subscription.Ĭontain the history of sign-in activity and audit trail of changes made in Azure AD for a particular tenant. Use the Activity log to determine the what, who, and when for any write operations (PUT, POST, DELETE) taken on the resources in your subscription. Provides insight into the operations on each Azure resource in the subscription from the outside (the management plane) in addition to updates on Service Health events.

The Azure Platform provides different types of logging.

Azure ad audit logs