Account/Authentication - Azure Active Directory - Ensure Self-Service Password Reset is Enabled

By Ashwin Venugopal -

 









Summary

If self-service password reset is enabled, it will allow the users to easily reset their own passwords in Azure AD. So, whenever your users sign in to Microsoft 365, they will have to provide additional contact information to help reset their passwords in the future and if combined registration is enabled, extra information outside MFA will not be required. As of August 2020, combined registration is enabled by default.

Reason

After this, users will not have to depend on the helpdesk to reset their passwords and moreover, this mechanism will automatically block the common, easily guessable passwords. Combined registrations should be enabled (if not already by default), as it will save the users from the hassle of registering for password reset separately from MFA.

What If?

We all know that, this setting will require the users to provide additional contact information in order to get enrolled in the self-service password reset along with some minor user education who are habitual of calling a helpdesk for password reset assistance and since combined registration is enabled automatically for new tenants, the users are not required to register for password reset separately from MFA.
Note- This will not work with Azure AD Connect/Sync.

How to?

To enable self-service password reset, use the Microsoft 365 Admin Center:
  1. Under Admin centers select Azure Active Directory.
  2. Now, choose Users via left hand navigation.
  3. Select Password reset.
  4. Select All under Self service password reset  enabled on the Properties page.
  5. Select Save.

      
Monitor:

To verify self-service password reset is enabled, use Microsoft 365 Admin Center:
  1. Under Admin centers select Azure Active Directory.
  2. Now, choose Users via left hand navigation.
  3. Select Password reset.
  4. Select All under Self service password reset enabled on the Properties page.










































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 groups of computers, re
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 of alert rule parameter
Read more

Design Planning (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Complex Organizational Structures SIEM can be an expensive security control, hence, it is common multiple businesses to contribute to the overall expense. Various organizational units may require a level of access to specific dashboards or sets of data. Microsoft Sentinel offers the ability to assign table-level permissions and limit the level of access to the minimum required to perform requisite job functions.  Role-based Access Control (RBAC) Requirements Microsoft Sentinel offers an extensive list of Azure built-in roles that can be used to provide granular access according to the job requirements and permitted level of access. Some of them are various Microsoft Sentinel dedicated roles: Microsoft Sentinel Contributor- Can perform all engineering-related configuration, such as creating alert rules, configuring data connectors, and additional similar tasks.  Microsoft Sentinel Reader- Can query the log data stor
Read more