Skip to content

Latest commit

 

History

History
29 lines (22 loc) · 3.21 KB

README.md

File metadata and controls

29 lines (22 loc) · 3.21 KB
Raw

Overview

This PowerShell script allows you to send a manual MFA notification (received through the Microsoft Authenticator app). Primary application for this is verifying a user's identity, such as for a password reset.

Requirements

  • PowerShell 5.1 (or higher)
  • The following modules
    • PSFramework (for logging, can switch to built-in Write-Output/Write-Host cmdlets if you don't want to rely on it)
    • CredentialManager (stores the MFA service principal password needed for adnotifications.windowsazure.com)
    • Microsoft.Graph.Applications (gets/sets the service principal password)
  • Microsoft 365 Global Admin

Azure App Registration

The app registration requires API permission Application.ReadWrite.All. Although this script defaults to certification authentication, it does support interactive. If you do use certificate authentication, it expects a certificate with common name of the app's client ID. (Modify $Script:AAD_CERT_CN if you want it to be something else.) When the script starts, it will automatically grab the most recent certificate (in your user's personal store) with that criteria for authentication.

MFA Service Principal

Again, you'll need to be a global admin so passwords can be set. It's possible there's a way to delegate permissions, but I haven't looked into it much (and I don't know that would affect this undocumented resource or the risks involved). If you want multiple users (such as helpdesk) to be able to issue requests, you can increase the default value of the EndDate parameter in Set-MgGraphServicePrincipalPassword. Otherwise, it would probably be best to put this behind a web app (particularly because the app requires Application.ReadWrite.All).

When the script runs, it will check if there's a stored credential (in Credential Manager) with the name of the MFA app's client ID. It appropriately sets a new one if it doesn't exist or the existing password expired. (These passwords, in Azure, don't delete themselves when they expire, and the script doesn't automatically remove them.)

Partner Center

One of the resources below (comments section) makes reference to needing a Microsoft Partner Center account. While creating an account is free, it's unnecessary. (Perhaps this was required when using the, soon to be deprecated, MSOnline module.) Regardless, a Partner Center account is not required for this script.

Number Matching

As this functionality was reverse-engineered from the NPS Extension, number matching isn't supported. The only thing I could get working is the basic Approve/Deny prompt. (There is mention of using OTP, but I couldn't get that to work.)

Resources

Thanks to the following for helping me piece this together: