- Chris Arceneaux (@chris_arceneaux)
- Fabian Kessler
This script leverages Veeam Backup for 365 (VB365) cmdlets and Microsoft Azure AD / Graph API cmdlets to validate whether access is present for the Microsoft Teams Protected API referenced in the KB article.
More information on why this script is beneficial can be found here.
- Currently no known issues
When executing this script without parameters:
Ex: Get-ProtectedAPIStatus.ps1
- Veeam Backup for Microsoft 365 v6a
- The application certificate must be installed on the server
- This is most likely already the case.
- The following PowerShell modules are required (and will be installed automagically if they are not present):
When executing this script with parameters:
Ex: Get-ProtectedAPIStatus.ps1 -TenantId "46c4fd38-f62b-4ff6-ac91-d1165a427804" -AppId "19ea5b98-ec35-4a4d-c6f9-9690403c6948" -CertThumbprint "60F50AEB325B119BB63929D0C430AAB223938ABF"
- The application certificate must be installed on the server
- The following PowerShell module is required (and will be installed automagically if it is not present):
Script contains built-in documentation which can be accessed using the typical PowerShell method:
Get-Help .\Get-ProtectedAPIStatus.ps1 -Full