Volg deze stappen om een Microsoft Azure-applicatie te maken in de Azure-portal. Als u de geavanceerde methode voor gegevensimport gebruikt om Microsoft Teams-gegevens naar uw Google Workspace-accounts te kopiëren, hebt u de Azure-applicatie nodig om een veilige gegevensimport te garanderen. U kunt kiezen uit twee methoden:
- Gebruik een PowerShell-script om een automatische verbinding in te stellen.
- Gebruik Azure Active Directory om een handmatige verbinding in te stellen.
Gebruik een PowerShell-script om een automatische verbinding in te stellen.
U moet een beheerder met een globale of bevoorrechte rol zijn om deze stappen te kunnen uitvoeren.
Optie 1: Azure Cloud Shell gebruiken
- Meld u als beheerder aan bij uw Azure-portal.
- Klik op Cloud Shell
PowerShell .
- Maak indien nodig een opslagaccount aan en accepteer de standaardinstellingen.
- Om de applicatie te maken, voert u de volgende opdracht in en drukt u vervolgens op Enter :
Install-Module Microsoft.Graph -Scope CurrentUser
- Als u een melding krijgt om te installeren vanuit een niet-vertrouwde repository, typ dan Y en klik vervolgens op Enter .
- Kopieer het volgende codeblok, plak het in PowerShell en druk op Enter .
<# .SYNOPSIS Automates the creation of a Single-Tenant Entra ID App for Workspace Migration. Strictly forces account selection and verifies specific Admin roles. #> # Check if the module is missing if (-not (Get-Module -ListAvailable -Name Microsoft.Graph.Authentication)) { Write-Host "Microsoft Graph module is NOT installed." -ForegroundColor Yellow $UserResponse = Read-Host "Would you like to try installing Microsoft Graph? (Y/N)" if ($UserResponse -ieq "Y") { try { # Use only native cmdlets, no .NET property setting Install-Module -Name Microsoft.Graph -Scope CurrentUser -Force -AllowClobber Write-Host "Installation complete!" -ForegroundColor Green } catch { Write-Error "Policy is blocking installation. Please contact IT to install Microsoft.Graph module." Read-Host "Press Enter to exit"; exit } } else { exit } } else { Write-Host "Microsoft Graph modules detected. Proceeding..." -ForegroundColor Green } # --- STEP 0: THE "DEEP" LOGOUT --- Write-Host "Forcing session cleanup..." -ForegroundColor Gray Disconnect-MgGraph -ErrorAction SilentlyContinue # Force clear the local token cache folder if it exists $CachePath = "$env:USERPROFILE\.mg" if (Test-Path $CachePath) { try { Remove-Item $CachePath -Recurse -Force -ErrorAction SilentlyContinue } catch {} } Write-Host "Opening Microsoft Login... (Please select the correct account)" -ForegroundColor Cyan $RequiredScopes = @( "Application.ReadWrite.All", "AppRoleAssignment.ReadWrite.All", "Directory.Read.All", "RoleManagement.Read.Directory" ) try { # In v2, -ContextScope Process is the most reliable way to force account selection # and prevent the session from saving to the machine permanently. Connect-MgGraph -Scopes $RequiredScopes -ContextScope Process $Context = Get-MgContext if ($null -eq $Context) { throw "Login was cancelled or failed." } $UserPrincipal = $Context.Account Write-Host "Logged in as: $UserPrincipal" -ForegroundColor Green # --- ROLE VALIDATION --- Write-Host "Verifying Directory Roles..." -ForegroundColor Gray $UserRoles = Get-MgUserMemberOf -UserId $Context.Account -All | Where-Object { $_.AdditionalProperties.displayName -ne $null } $Authorized = $false $RequiredRoles = @("Global Administrator", "Privileged Role Administrator") foreach ($role in $UserRoles) { $roleName = $role.AdditionalProperties.displayName if ($roleName -in $RequiredRoles) { $Authorized = $true Write-Host "Access Granted: $roleName" -ForegroundColor Green break } } if (-not $Authorized) { Write-Host "`nCRITICAL ERROR: Insufficient Privileges." -ForegroundColor Red Write-Host "Account must be 'Global Administrator' or 'Privileged Role Administrator'." -ForegroundColor Yellow Disconnect-MgGraph Read-Host "`nPress Enter to exit"; exit } } catch { Write-Error "Login failed: $_" Read-Host "Press Enter to exit"; exit } # --- USER INPUT --- Write-Host "`n--- APPLICATION SETUP ---" -ForegroundColor Cyan $InputName = Read-Host "Enter the name for your new Entra ID Application (Default: Workspace Migration App)" $AppName = if ([string]::IsNullOrWhiteSpace($InputName)) { "Workspace Migration App" } else { $InputName } # --- CONFIGURATION --- # Updated Map containing all the requested application permissions $PermissionMap = @{ "member.read.hidden" = "Member.Read.Hidden" "organization.read.all" = "Organization.Read.All" "channelmember.read.all" = "ChannelMember.Read.All" "channelmessage.read.all" = "ChannelMessage.Read.All" "channelsettings.read.all" = "ChannelSettings.Read.All" "group.read.all" = "Group.Read.All" "team.readbasic.all" = "Team.ReadBasic.All" "teammember.read.all" = "TeamMember.Read.All" "user.read.all" = "User.Read.All" “application.read.all” = “Application.Read.All” } $TenantId = $Context.TenantId $GraphAppId = "00000003-0000-0000-c000-000000000000" try { # --- STEP 1: REGISTER APPLICATION --- Write-Host "Creating Application: $AppName..." -ForegroundColor Cyan $Application = New-MgApplication -BodyParameter @{ displayName = $AppName signInAudience = "AzureADMyOrg" } # --- STEP 2: PREPARE SERVICE PRINCIPAL --- $NewServicePrincipal = New-MgServicePrincipal -BodyParameter @{ appId = $Application.AppId } Write-Host "Waiting 10 seconds for replication..." -ForegroundColor DarkGray Start-Sleep -Seconds 10 # --- STEP 3: CONFIGURE & GRANT PERMISSIONS --- Write-Host "Configuring API Permissions & Granting Admin Consent..." -ForegroundColor Cyan $GraphSP = Get-MgServicePrincipal -Filter "AppId eq '$GraphAppId'" | Select-Object -First 1 $ResourceAccessList = @() foreach ($key in $PermissionMap.Keys) { $RealRoleName = $PermissionMap[$key] $Role = $GraphSP.AppRoles | Where-Object { $_.Value -eq $RealRoleName } if ($Role) { $ResourceAccessList += @{ id = $Role.Id; type = "Role" } New-MgServicePrincipalAppRoleAssignment -ServicePrincipalId $NewServicePrincipal.Id -BodyParameter @{ principalId = $NewServicePrincipal.Id resourceId = $GraphSP.Id appRoleId = $Role.Id } | Out-Null Write-Host " - Granted: $RealRoleName" -ForegroundColor Gray } } Update-MgApplication -ApplicationId $Application.Id -RequiredResourceAccess @(@{ resourceAppId = $GraphAppId resourceAccess = $ResourceAccessList }) # --- STEP 4: CREATE CLIENT SECRET --- Write-Host "Generating Client Secret..." -ForegroundColor Cyan $ExpiryDate = (Get-Date).AddYears(2).ToUniversalTime().ToString("yyyy-MM-ddTHH:mm:ssZ") $PasswordCred = Add-MgApplicationPassword -ApplicationId $Application.Id -BodyParameter @{ passwordCredential = @{ displayName = "MigrationToolSecret" endDateTime = $ExpiryDate } } # --- OUTPUT --- Write-Host "`n-------------------------------------------------------" -ForegroundColor Yellow Write-Host " SETUP COMPLETE - SAVE THESE DETAILS" -ForegroundColor Yellow Write-Host "-------------------------------------------------------" -ForegroundColor Yellow Write-Host "Application Name : $AppName" Write-Host "Application (Client) ID : $($Application.AppId)" Write-Host "Client Secret Value : $($PasswordCred.SecretText)" Write-Host "Directory (Tenant) ID : $TenantId" Write-Warning "IMPORTANT: Copy the Client Secret Value immediately." } catch { Write-Error "Operation failed: $_" } # --- FINAL DISCONNECT --- Disconnect-MgGraph Read-Host "`nPress Enter to close this window"
- Noteer de volgende inloggegevens en bewaar ze veilig. Als de inloggegevens uitlekken, kunnen hackers toegang krijgen tot al uw Teams-gegevens.
- Klantgeheim
- Applicatie-ID (client-ID)
- Directory (tenant) ID
Optie 2: Windows PowerShell gebruiken
- Maak in Windows een nieuw platte tekstbestand aan en noem het migration_app_creator.ps1 .
- Kopieer het volgende codeblok, plak het in het nieuwe bestand en klik op 'Uitvoeren met PowerShell' .
<# .SYNOPSIS Automates the creation of a Single-Tenant Entra ID App for Workspace Migration. Strictly forces account selection and verifies specific Admin roles. #> # Check if the module is missing if (-not (Get-Module -ListAvailable -Name Microsoft.Graph.Authentication)) { Write-Host "Microsoft Graph module is NOT installed." -ForegroundColor Yellow $UserResponse = Read-Host "Would you like to try installing Microsoft Graph? (Y/N)" if ($UserResponse -ieq "Y") { try { # Use only native cmdlets, no .NET property setting Install-Module -Name Microsoft.Graph -Scope CurrentUser -Force -AllowClobber Write-Host "Installation complete!" -ForegroundColor Green } catch { Write-Error "Policy is blocking installation. Please contact IT to install Microsoft.Graph module." Read-Host "Press Enter to exit"; exit } } else { exit } } else { Write-Host "Microsoft Graph modules detected. Proceeding..." -ForegroundColor Green } # --- STEP 0: THE "DEEP" LOGOUT --- Write-Host "Forcing session cleanup..." -ForegroundColor Gray Disconnect-MgGraph -ErrorAction SilentlyContinue # Force clear the local token cache folder if it exists $CachePath = "$env:USERPROFILE\.mg" if (Test-Path $CachePath) { try { Remove-Item $CachePath -Recurse -Force -ErrorAction SilentlyContinue } catch {} } Write-Host "Opening Microsoft Login... (Please select the correct account)" -ForegroundColor Cyan $RequiredScopes = @( "Application.ReadWrite.All", "AppRoleAssignment.ReadWrite.All", "Directory.Read.All", "RoleManagement.Read.Directory" ) try { # In v2, -ContextScope Process is the most reliable way to force account selection # and prevent the session from saving to the machine permanently. Connect-MgGraph -Scopes $RequiredScopes -ContextScope Process $Context = Get-MgContext if ($null -eq $Context) { throw "Login was cancelled or failed." } $UserPrincipal = $Context.Account Write-Host "Logged in as: $UserPrincipal" -ForegroundColor Green # --- ROLE VALIDATION --- Write-Host "Verifying Directory Roles..." -ForegroundColor Gray $UserRoles = Get-MgUserMemberOf -UserId $Context.Account -All | Where-Object { $_.AdditionalProperties.displayName -ne $null } $Authorized = $false $RequiredRoles = @("Global Administrator", "Privileged Role Administrator") foreach ($role in $UserRoles) { $roleName = $role.AdditionalProperties.displayName if ($roleName -in $RequiredRoles) { $Authorized = $true Write-Host "Access Granted: $roleName" -ForegroundColor Green break } } if (-not $Authorized) { Write-Host "`nCRITICAL ERROR: Insufficient Privileges." -ForegroundColor Red Write-Host "Account must be 'Global Administrator' or 'Privileged Role Administrator'." -ForegroundColor Yellow Disconnect-MgGraph Read-Host "`nPress Enter to exit"; exit } } catch { Write-Error "Login failed: $_" Read-Host "Press Enter to exit"; exit } # --- USER INPUT --- Write-Host "`n--- APPLICATION SETUP ---" -ForegroundColor Cyan $InputName = Read-Host "Enter the name for your new Entra ID Application (Default: Workspace Migration App)" $AppName = if ([string]::IsNullOrWhiteSpace($InputName)) { "Workspace Migration App" } else { $InputName } # --- CONFIGURATION --- # Updated Map containing all the requested application permissions $PermissionMap = @{ "member.read.hidden" = "Member.Read.Hidden" "organization.read.all" = "Organization.Read.All" "channelmember.read.all" = "ChannelMember.Read.All" "channelmessage.read.all" = "ChannelMessage.Read.All" "channelsettings.read.all" = "ChannelSettings.Read.All" "group.read.all" = "Group.Read.All" "team.readbasic.all" = "Team.ReadBasic.All" "teammember.read.all" = "TeamMember.Read.All" "user.read.all" = "User.Read.All" “application.read.all” = “Application.Read.All” } $TenantId = $Context.TenantId $GraphAppId = "00000003-0000-0000-c000-000000000000" try { # --- STEP 1: REGISTER APPLICATION --- Write-Host "Creating Application: $AppName..." -ForegroundColor Cyan $Application = New-MgApplication -BodyParameter @{ displayName = $AppName signInAudience = "AzureADMyOrg" } # --- STEP 2: PREPARE SERVICE PRINCIPAL --- $NewServicePrincipal = New-MgServicePrincipal -BodyParameter @{ appId = $Application.AppId } Write-Host "Waiting 10 seconds for replication..." -ForegroundColor DarkGray Start-Sleep -Seconds 10 # --- STEP 3: CONFIGURE & GRANT PERMISSIONS --- Write-Host "Configuring API Permissions & Granting Admin Consent..." -ForegroundColor Cyan $GraphSP = Get-MgServicePrincipal -Filter "AppId eq '$GraphAppId'" | Select-Object -First 1 $ResourceAccessList = @() foreach ($key in $PermissionMap.Keys) { $RealRoleName = $PermissionMap[$key] $Role = $GraphSP.AppRoles | Where-Object { $_.Value -eq $RealRoleName } if ($Role) { $ResourceAccessList += @{ id = $Role.Id; type = "Role" } New-MgServicePrincipalAppRoleAssignment -ServicePrincipalId $NewServicePrincipal.Id -BodyParameter @{ principalId = $NewServicePrincipal.Id resourceId = $GraphSP.Id appRoleId = $Role.Id } | Out-Null Write-Host " - Granted: $RealRoleName" -ForegroundColor Gray } } Update-MgApplication -ApplicationId $Application.Id -RequiredResourceAccess @(@{ resourceAppId = $GraphAppId resourceAccess = $ResourceAccessList }) # --- STEP 4: CREATE CLIENT SECRET --- Write-Host "Generating Client Secret..." -ForegroundColor Cyan $ExpiryDate = (Get-Date).AddYears(2).ToUniversalTime().ToString("yyyy-MM-ddTHH:mm:ssZ") $PasswordCred = Add-MgApplicationPassword -ApplicationId $Application.Id -BodyParameter @{ passwordCredential = @{ displayName = "MigrationToolSecret" endDateTime = $ExpiryDate } } # --- OUTPUT --- Write-Host "`n-------------------------------------------------------" -ForegroundColor Yellow Write-Host " SETUP COMPLETE - SAVE THESE DETAILS" -ForegroundColor Yellow Write-Host "-------------------------------------------------------" -ForegroundColor Yellow Write-Host "Application Name : $AppName" Write-Host "Application (Client) ID : $($Application.AppId)" Write-Host "Client Secret Value : $($PasswordCred.SecretText)" Write-Host "Directory (Tenant) ID : $TenantId" Write-Warning "IMPORTANT: Copy the Client Secret Value immediately." } catch { Write-Error "Operation failed: $_" } # --- FINAL DISCONNECT --- Disconnect-MgGraph Read-Host "`nPress Enter to close this window"
- Klantgeheim
- Applicatie-ID (client-ID)
- Directory (tenant) ID
Gebruik Azure Active Directory om een handmatige verbinding in te stellen.
De specifieke stappen van Microsoft kunnen variëren afhankelijk van uw Azure-portalversie en updates van Microsoft. Raadpleeg de documentatie van Microsoft voor de meest recente richtlijnen voor app-registratie en -autorisatie.
Stap 1: Een nieuwe aanvraag registreren
Om veiligheidsredenen raden wij u aan de nieuwe applicatie als een single tenant te registreren.
- Meld u als beheerder aan bij uw Azure-portal.
- Ga in Azure Active Directory (Azure AD) naar App-registraties .
- Klik op Nieuwe registratie en voer een naam in voor uw applicatie (bijvoorbeeld Geavanceerde import-app).
- Voor ondersteunde accounttypen klikt u op 'Accounts in deze organisatiedirectory' om een applicatie voor één tenant te maken.
- Klik op Registreren .
Stap 2: API-machtigingen configureren
Kies een van de volgende opties:
Optie 1: Handmatig machtigingen toevoegen
- Klik aan de zijkant, onder 'Beheren' , op 'API-machtigingen '.
- Klik op ' Een machtiging toevoegen'.
Microsoft API's
Microsoft Graph .
- Selecteer voor toepassingsmachtigingen :
- Applicatie.Lees.Alles
- Kanaallid.Lees.Alles
- Kanaalbericht.Lees.Alles
- Kanaalinstellingen.Lees.Alles
- Groep.Lees.Alles
- Lid.Lezen.Verborgen
- Organisatie.Lees.Alles
- Team.ReadBasic.All
- Teamlid.Lees.Alles
- Gebruiker.Leest.Alles
- Klik op Beheerderstoestemming verlenen voor uw organisatie .
Optie 2: Bewerk het toepassingsmanifest
- Open het applicatiemanifest.
- Ga naar “resourceAccess” : [ ] en kies een optie:
- Als “resourceAccess” : [ ] al een waarde heeft, voeg dan een komma toe en plak vervolgens het volgende codeblok.
- Als “resourceAccess” : [ ] geen waarde heeft, kopieer en plak dan het volgende codeblok.
{ "id": "658aa5d8-239f-45c4-aa12-864f4fc7e490", "type": "Role" },
{ "id": "498476ce-e0fe-48b0-b801-37ba7e2685c6", "type": "Role" },
{ "id": "3b55498e-47ec-484f-8136-9013221c06a9", "type": "Role" },
{ "id": "7b2449af-6ccd-4f4d-9f78-e550c193f0d1", "type": "Role" },
{ "id": "c97b873f-f59f-49aa-8a0e-52b32d762124", "type": "Role" },
{ "id": "5b567255-7703-4780-807c-7be8301ae99b", "type": "Role" },
{ "id": "2280dda6-0bfd-44ee-a2f4-cb867cfc4c1e", "type": "Role" },
{ "id": "660b7406-55f1-41ca-a0ed-0b035e182f3e", "type": "Role" },
{ "id": "df021288-bdef-4463-88db-98f22de89214", "type": "Role" },
{ "id": "9a5d68dd-52b0-4cc2-bd40-abcf44ac3a30", "type": "Role" }
- Klik op Beheerderstoestemming verlenen voor uw organisatie .
Stap 3: Genereer het clientgeheim
- Klik aan de zijkant bij 'Beheren' op 'Certificaten en geheimen'.
Nieuw clientgeheim .
- Voer een beschrijving in, selecteer een vervaldatum en klik op Toevoegen .
- Kopieer de waarde van het clientgeheim en bewaar deze veilig. De waarde wordt slechts één keer weergegeven.
Stap 4: Verzamel de applicatiegegevens
Belangrijk : Bewaar de inloggegevens voor de applicatie veilig. Als de inloggegevens lekken, kunnen hackers toegang krijgen tot al uw Teams-gegevens.
Klik op Overzicht en noteer de volgende gegevens veilig:
- Applicatie-ID (client-ID)
- Directory (tenant) ID
Google, Google Workspace en aanverwante merken en logo's zijn handelsmerken van Google LLC. Alle andere bedrijfs- en productnamen zijn handelsmerken van de bedrijven waaraan ze zijn verbonden.