📋 Microsoft Entra Documentation Changes

Daily summary for changes since March 7th 2026, 8:24 PM PST

Report generated on March 8th 2026, 9:24 PM PDT

📊 Summary

13
Total Commits
0
New Files
2
Modified Files
0
Deleted Files
5
Contributors

📝 Modified Documentation Files

Modified by Ken Withee on Mar 8, 2026 9:59 PM
📖 View on learn.microsoft.com
+10 / -15 lines changed
Commit: Address audit: fix scopes, -All flag, deduplicate steps
Changes:
Before
After
 
3. Create or use a managed administrative account from the tenant that you want to delete. For example: `[email protected]`.
 
4. Open PowerShell and connect to Microsoft Entra ID by using admin credentials with the following command: `Connect-MgGraph -Scopes "Application.ReadWrite.All", "Directory.ReadWrite.All"`
 
>[!WARNING]
> You must run PowerShell by using admin credentials for the tenant that you're trying to delete. Only homed-in admins have access to manage the directory via Powershell. You can't use guest user admins, Microsoft accounts, or multiple directories.
>
> Before you proceed, verify that you're connected to the tenant that you want to delete with the Microsoft Graph PowerShell module. We recommend that you run the `Get-MgDomain` command to confirm that you're connected to the correct tenant ID and `onmicrosoft.com` domain.
 
5. Run the following commands to set the tenant context. The `Connect-AzAccount` command authenticates to the Az PowerShell module, which is separate from the Microsoft Graph connection established in step 4. Both connections are needed for the remaining steps. **Don't skip these steps or you risk deleting enterprise apps from the wrong tenant.**
 
```powershell
Clear-AzContext -Scope CurrentUser
>[!WARNING]
> Before you proceed, verify that you're connected to the tenant that you want to delete with the Az PowerShell module. We recommend that you run the `Get-AzContext` command to check the connected tenant ID and `onmicrosoft.com` domain. Do NOT skip the above steps or you run the risk of deleting enterprise apps from the wrong tenant.
 
6. Run the following command to remove any enterprise apps that you can't delete:
 
```powershell
 
3. Create or use a managed administrative account from the tenant that you want to delete. For example: `[email protected]`.
 
4. Open PowerShell and connect to Microsoft Entra ID by using admin credentials with the following command: `Connect-MgGraph -Scopes "Application.ReadWrite.All"`
 
>[!WARNING]
> You must run PowerShell by using admin credentials for the tenant that you're trying to delete. Only homed-in admins have access to manage the directory via Powershell. You can't use guest user admins, Microsoft accounts, or multiple directories.
>
> Before you proceed, verify that you're connected to the tenant that you want to delete with the Microsoft Graph PowerShell module. We recommend that you run the `Get-MgDomain` command to confirm that you're connected to the correct tenant ID and `onmicrosoft.com` domain.
 
5. Run the following commands to verify your tenant context with the Az PowerShell module. This step is a safety check to confirm you're connected to the correct tenant. **Don't skip these steps or you risk deleting enterprise apps from the wrong tenant.**
 
```powershell
Clear-AzContext -Scope CurrentUser
>[!WARNING]
> Before you proceed, verify that you're connected to the tenant that you want to delete with the Az PowerShell module. We recommend that you run the `Get-AzContext` command to check the connected tenant ID and `onmicrosoft.com` domain. Do NOT skip the above steps or you run the risk of deleting enterprise apps from the wrong tenant.
 
6. Run the following command to remove service principals. Run the command multiple times until all service principals are removed, since some might fail on the first attempt due to dependencies.
 
```powershell
+2 / -2 lines changed
Commit: Fix licensed/error counts using Get-MgGroupMemberWithLicenseError
Changes:
Before
After
$groupInfo | Add-Member -MemberType NoteProperty -Name "Group ID" -Value $group.Id
$groupInfo | Add-Member -MemberType NoteProperty -Name "License Types" -Value ($group.AssignedLicenses | Select-Object -ExpandProperty SkuId)
$groupInfo | Add-Member -MemberType NoteProperty -Name "Total User Count" -Value (Get-MgGroupMember -GroupId $group.Id -All | Measure-Object).Count
$groupInfo | Add-Member -MemberType NoteProperty -Name "Licensed User Count" -Value (Get-MgGroupMember -GroupId $group.Id -All | Measure-Object).Count
$groupInfo | Add-Member -MemberType NoteProperty -Name "License Error Count" -Value (Get-MgGroup -GroupId $group.Id -Property LicenseProcessingState).LicenseProcessingState.State
$groupInfoArray += $groupInfo
}
 
$groupInfo | Add-Member -MemberType NoteProperty -Name "Group ID" -Value $group.Id
$groupInfo | Add-Member -MemberType NoteProperty -Name "License Types" -Value ($group.AssignedLicenses | Select-Object -ExpandProperty SkuId)
$groupInfo | Add-Member -MemberType NoteProperty -Name "Total User Count" -Value (Get-MgGroupMember -GroupId $group.Id -All | Measure-Object).Count
$groupInfo | Add-Member -MemberType NoteProperty -Name "License Error Count" -Value (Get-MgGroupMemberWithLicenseError -GroupId $group.Id -All | Measure-Object).Count
$groupInfo | Add-Member -MemberType NoteProperty -Name "Licensed User Count" -Value ((Get-MgGroupMember -GroupId $group.Id -All | Measure-Object).Count - (Get-MgGroupMemberWithLicenseError -GroupId $group.Id -All | Measure-Object).Count)
$groupInfoArray += $groupInfo
}