Self-Service Password Reset Via Lockscreen

Akins IT • July 11, 2018
Connect with us

The Need:


Password resets can often be burdensome for an organization’s help desk team, and being locked out of an account or device can leave users without access to their work at the most inconvenient times. Through Self-Service Password Reset (SSPR), integrated with Azure Active Directory, users in the office can easily regain access to their work in a secure manner, as needed. But did you know remote users (i.e. at home, onsite, off premise) can also regain access securely? This is accomplished through Azure AD without utilizing a VPN to connect to the organizations on-premise Active Directory. Remote users can reset their password via the Microsoft Cloud, which is then transcribed into Azure AD. Since the company is already utilizing Azure AD Connect, Azure AD can easily write the new password back to the local on-premise Active Directory. This feature not only relieves the burden from the organization’s help desk team, it also allows the user to regain access in a timely manner and return to work.

One of the largest problems surrounding SSPR is not the deployment of the services, but the user training surrounding it. With Windows 10 Build 1803, things just became a whole lot simpler in regards to the user training and process. I am going to first take you through the prerequisites for SSPR and then talk about how things have changed with Windows 10 April 2018 Update (Build 1803).


The Prerequisites:


There are a few Microsoft Services that are perquisites to SSPR if you are in a Hybrid Active Directory Environment utilizing Azure Active Directory Connect (AAD):

 

  • Password Writeback must be setup and enabled within AAD Connect.
  • Permissions within your local Active Directory must be setup with the AAD Connect Connector Account.
  • Multi-Factor Authentication (MFA) should also be rolled out within your environment.
  • Register your users for SSPR.

The User Experience


Once you have successfully deployed SSPR within your organization users normally have to visit https://passwordreset.microsoftonline.com/ in order to reset their password. The issue with this is users must have access to another device in order to access the website. When traveling or in other business predicaments, users may only have access to the device they are locked out of. This is where one of the new features within Windows 10 1803 saves the day! Utilizing Microsoft Intune a Mobile Device Management (MDM) platform, a part of the Microsoft EMS Suite, administrators are able to push out a policy enabling SSPR on the users Windows 10 Lock screen. Now that is pretty cool!

Once clicked, users will be taken through the SSPR process.

Once the process is completed, the password will be written back to your local Active Directory immediately and the user will be able to sign-in to the device they were once locked out of. 


How do I enable this for my organization?


If you have already setup SSPR and your devices are Hybrid Azure AD joined or Azure AD joined, have a global admin configure an MDM policy, make sure your devices are running the latest version of Windows 10, and that’s it! Users will now see a “Reset password” link on their login screen.

Learn More About Azure AD
By Shawn Akins October 20, 2025
October 20, 2025 — Early today, Amazon Web Services experienced a major incident centered in its US‑EAST‑1 (N. Virginia) region. AWS reports the event began around 12:11 a.m. PT and tied back to DNS resolution affecting DynamoDB , with mitigation within a couple of hours and recovery continuing thereafter. As the outage rippled, popular services like Snapchat, Venmo, Ring, Roblox, Fortnite , and even some Amazon properties saw disruptions before recovering. If your apps or data are anchored to a single cloud, a morning like this can turn into a help‑desk fire drill. A multi‑cloud or cloud‑smart approach helps you ride through these moments with minimal end‑user impact. What happened (and why it matters) Single‑region fragility: US‑EAST‑1 is massive—and when it sneezes, the internet catches a cold. Incidents here have a history of wide blast radius. Shared dependencies: DNS issues to core services (like DynamoDB endpoints) can cascade across workloads that never directly “touch” that service. Multi‑cloud: practical resilience, not buzzwords For mid‑sized orgs, schools, and local government, multi‑cloud doesn’t have to mean “every app in every cloud.” It means thoughtful redundancy where it counts : Multi‑region or multi‑provider failover for critical apps Run active/standby across AWS and Azure (or another provider), or at least across two AWS regions with automated failover. Start with citizen‑facing portals, SIS/LMS access, emergency comms, and payment gateways. Portable platforms Use Kubernetes and containers, keep state externalized, and standardize infra with Terraform/Ansible so you can redeploy fast when a region (or a provider) wobbles. (Today’s DNS hiccup is exactly the kind of scenario this protects against.) Resilient data layers Replicate data asynchronously across clouds/regions; choose databases with cross‑region failover and test RPO/RTO quarterly. If you rely on a managed database tied to one region, design an escape hatch. Traffic and identity that float Use global traffic managers/DNS to shift users automatically; keep identity (MFA/SSO) highly available and not hard‑wired to a single provider’s control plane. Run the playbook Document health checks, automated cutover, and comms templates. Then practice —tabletops and live failovers. Many services today recovered within hours, but only teams with rehearsed playbooks avoided user‑visible downtime. The bottom line Cloud concentration risk is real. Outages will happen—what matters is whether your constituents, students, and staff feel it. A pragmatic multi‑cloud stance limits the blast radius and keeps your mission‑critical services online when one provider has a bad day. Need a resilience check? Akins IT can help you prioritize which systems should be multi‑cloud, design the right level of redundancy, and validate your failover plan—without overspending. Let’s start with a quick, 30‑minute review of your most critical services and RPO/RTO targets. (No slideware, just actionable next steps.)
By Shawn Akins October 13, 2025
How a Zero-Day in GoAnywhere MFT Sparked a Ransomware Wave—and What Mid-Sized IT Leaders Must Do Now
By Shawn Akins October 13, 2025
The clock is ticking: Learn your options for Windows 11 migration, Extended Security Updates, and cost‑smart strategies before support ends.
More Posts