Account/Authentication - Azure Active Directory - Ensure Modern Authentication for Exchange Online is Enabled

By Ashwin Venugopal -

 







Summary

The option of modern authentication in Microsoft 365 enables authentication features like Multifactor Authentication (MFA) using smart cards, Certificate-based Authentication (CBA), and third-party SAML identity providers; when it is enabled in Exchange Online, Outlook 2016 and Outlook 2013 use basic authentication to log in to Microsoft 365 mailboxes. 

When certain email clients like Outlook 2013 and Outlook 2016 are configured, the users have to authenticate with the help of enhanced authentication mechanisms, such as MFA. Other Outlook clients that are available in Microsoft 365 (like Outlook Mobile and Outlook for Mac 2016) generally use modern authentication to log in to Microsoft 365 mailboxes.

Reason

Authentication controls like MFAs can be circumvented if basic authentication is used by Exchange Online email clients such as Outlook 2016 and Outlook 2013. However, if modern authentication is enabled for Exchange Online, strong authentication mechanisms can be used while establishing sessions between email clients and Exchange Online.

What If?

Users older email clients, such as Outlook 2013 and Outlook 2016, will no longer be able to authenticate to Exchange using Basic Authentication, which will also necessitate migration to modern authentication practices.

How to?

To enable modern authentication, use the Exchange Online PowerShell Module:
  1. Run the Microsoft Exchange Online PowerShell Module.
  2. Connect to Exchange Online using Connect-ExchangeOnline.
  3. Run the following PowerShell command:
Set -OrganizationConfig -OAuth2ClientProfileEnabled $True

Monitor:

To verify modern authentication is enabled, use the Exchange Online PowerShell Module:
  1. Run the Microsoft Exchange Online PowerShell Module.
  2. Connect to Exchange Online using Connect-ExchangeOnline.
  3. Run the following PowerShell command:

    4. Get -OrganizationConfig | Format -Table -Auto Name, OAuth*

       4. Verify OAuth2ClientProfileEnabled is True.









































Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning...
Read more