fix accesstoken type (#3211)

Co-authored-by: freddydk <[email protected]>

AzureAD/New-AadAppsForBc.ps1

@@ -79,16 +79,20 @@ try {
             if ($jwtToken.aud -ne 'https://graph.microsoft.com') {
                 Write-Host -ForegroundColor Yellow "The accesstoken was provided for $($jwtToken.aud), should have been for https://graph.microsoft.com"
             }
-            Connect-MgGraph -AccessToken $bcAuthContext.accessToken | Out-Null
+            $accessToken = $bcAuthContext.accessToken
         }
-        else {
-            if ($accessToken) {
-                Connect-MgGraph -accessToken $accessToken | Out-Null
+        if ($accessToken) {
+            try {
+                # Connect-MgGraph changed type of accesstoken parameter from plain text to securestring along the way
+                Connect-MgGraph -accessToken (ConvertTo-SecureString -String $accessToken -AsPlainText -Force) | Out-Null
             }
-            else {
-                Connect-MgGraph -Scopes 'Application.ReadWrite.All' | Out-Null
+            catch [System.ArgumentException] {
+                Connect-MgGraph -accessToken $accessToken | Out-Null
             }
         }
+        else {
+            Connect-MgGraph -Scopes 'Application.ReadWrite.All' | Out-Null
+        }
     }
     $account = Get-MgContext
 

ReleaseNotes.txt

@@ -1,3 +1,6 @@
+6.0.1
+New-AadAppsForBC doesn't work with the newer versions of Microsoft.Graph module (where the type of the accesstoken parameter has changed)
+
 6.0.0
 Add parameter -accept_insiderEULA on New-BcContainer, Get-BcArtifactUrl and Run-AlPipeline to accept the insider EULA (https://go.microsoft.com/fwlink/?linkid=2245051) instead of using the insider SAS token.
 The insider SAS token is still supported until April 2024 where the last insider SAS token will expire...

Version.txt

@@ -1 +1 @@
-6.0.0-dev
+6.0.1-dev