Automating with PowerShell: Disabling application consent on all tenants

Before we get into this, I recently setup a new CyberDrain Discord server for questions about CIPP, and the CTFs I give. Join our discord here

I’ve blogged about monitoring the settings to approving application consent not too long ago, where I’ve discussed that it’s annoying we don’t have a central way of doing this without the MSOL module. The MSOL module is considered deprecated and can’t be used with modern PowerShell, or within Azure Functions without getting deserialized objects back.

This method allows you to disable application consent without using the MSOL module, and allows you to run that for all your tenants, giving you more options to use in your automation.

Fair warning’; the script also disables iOS native mail mail. To enable those you can simply visit this link and give consent for that tenant, unfortunately there is no process for that yet. Remember to change the link to your specific tenant ID.

https://login.microsoftonline.com/<YOURONMICROSOFT.COM>/oauth2/authorize?client_id=f8d98a96-0999-43f5-8af3-69971c7bb423&response_type=code&redirect_uri=com.apple.Preferences://oauth-redirect/&prompt=admin_consent

Single tenant script

As is the case with most of my scripts, you’ll need your secure application model for this. Specifically your Exchange Refresh Token.

$Tenant = "YourTenant.Onmicrosoft.com"
$ENV:ExchangeRefreshToken = "YourLongRefreshToken"

try {
    $uri = "https://login.microsoftonline.com/$($Tenant)/oauth2/token"
    $body = "resource=https://admin.microsoft.com&grant_type=refresh_token&refresh_token=$($ENV:ExchangeRefreshToken)"
    $token = Invoke-RestMethod $uri -Body $body -ContentType "application/x-www-form-urlencoded" -ErrorAction SilentlyContinue -Method post
    $oAuth = Invoke-RestMethod -ContentType "application/json;charset=UTF-8" -Uri 'https://admin.microsoft.com/admin/api/settings/apps/IntegratedApps' -Body '{"Enabled":false}' -Method POST -Headers @{
        Authorization            = "Bearer $($token.access_token)";
        "x-ms-client-request-id" = [guid]::NewGuid().ToString();
        "x-ms-client-session-id" = [guid]::NewGuid().ToString()
        'x-ms-correlation-id'    = [guid]::NewGuid()
        'X-Requested-With'       = 'XMLHttpRequest'
    }

}
catch {
write-error "Failed to apply Application Consent Mode Error: $($_.exception.message)"
}

Multiple Tenant Script

This script loops through all your tenants and makes sure it’s disabled everywhere. Just be sure that you don’t have any legacy application users when running this, and remember that this does not remove consent that has already been granted.

#
$ApplicationId = 'AppID'
$ApplicationSecret = 'AppSecret'
$RefreshToken = 'RefreshTokens'
$ENV:ExchangeRefreshToken = 'YourExchangeRefreshToken'
#
$credential = New-Object System.Management.Automation.PSCredential($ApplicationId, ($ApplicationSecret | Convertto-SecureString -AsPlainText -Force))
$graphToken = New-PartnerAccessToken -ApplicationId $ApplicationId -Credential $credential -RefreshToken $refreshToken -Scopes 'https://graph.microsoft.com/.default' -ServicePrincipal

write-host "Connecting to the Graph API to get all tenants." -ForegroundColor Green
$Contractheaders = @{ "Authorization" = "Bearer $($graphToken.accesstoken)" }
$Customers = (Invoke-RestMethod -Uri "https://graph.microsoft.com/v1.0/contracts?`$top=999" -Method GET -Headers $Contractheaders).value
foreach ($Customer in $Customers) {
try {
    $uri = "https://login.microsoftonline.com/$($customer.customerid)/oauth2/token"
    $body = "resource=https://admin.microsoft.com&grant_type=refresh_token&refresh_token=$($ENV:ExchangeRefreshToken)"
    $token = Invoke-RestMethod $uri -Body $body -ContentType "application/x-www-form-urlencoded" -ErrorAction SilentlyContinue -Method post
    $oAuth = Invoke-RestMethod -ContentType "application/json;charset=UTF-8" -Uri 'https://admin.microsoft.com/admin/api/settings/apps/IntegratedApps' -Body '{"Enabled":false}' -Method POST -Headers @{
        Authorization            = "Bearer $($token.access_token)";
        "x-ms-client-request-id" = [guid]::NewGuid().ToString();
        "x-ms-client-session-id" = [guid]::NewGuid().ToString()
        'x-ms-correlation-id'    = [guid]::NewGuid()
        'X-Requested-With'       = 'XMLHttpRequest'
    }
    Log-request -API "Standards" -tenant $tenant -message  "Application Consent Mode has been enabled." -sev Info
}
catch {
    Log-request -API "Standards" -tenant $tenant -message  "Failed to apply Application Consent Mode Error: $($_.exception.message)" -sev Error
}
}

As always, I hope you enjoy and happy PowerShelling! 🙂

Recent Articles

Automating with PowerShell: making stolen tokens useless with Global Secure Access

Last week I watched Merill Fernando talk to Alex Pavlovsky and Marilee Tuscak from the Entra team about something I’d kinda put under the “needs a GSA licence” branch and i’d check it out later, turns out that like most people, I half-assed the documentation and it turns out it doesn’t. There’s two features that come with any P1 license; Compliant network check and Source IP Restoration. So BP, P1, or even frontline worker licenses already have this.

CIPP ❤️ #IntuneForMSPs

We’re Joining #IntuneForMSPs 🎉

Being invited by Microsoft to join a global initiative is a big moment for us, and we want to be clear about why it matters. #IntuneForMSPs is Microsoft’s program to help MSPs deliver Microsoft 365, Intune, and Copilot services at scale, and CIPP is now part of it, bringing the largest MSP community in the channel directly to Microsoft.

The return of CyberDrain CTF

CyberDrain CTF returns! (and so do I!)

It’s been since september that I actually picked up a digital pen equivalent and wrote anything down. This was due to me being busy with life but also my side projects like CIPP. I’m trying to get back into the game of scripting and blogging about these scripts. There’s still so much to automate and so little time, right? ;)