@microsoft/teamsfx-core 2.0.6-alpha.e73e76fb5.0 → 2.0.6-alpha.e92fb7848.0

package/templates/plugins/resource/aad/auth/bot/README.md

@@ -2,20 +2,20 @@
 
 > Note: This document includes single sign-on instructions applicable for both bot and message extension. Make sure to add the corresponding Teams capability first and then follow the documentation.
 
-Microsoft Teams provides a mechanism by which an application can obtain the signed-in Teams user token to access Microsoft Graph (and other APIs). Teams Toolkit facilitates this interaction by abstracting some of the Azure Active Directory (AAD) flows and integrations behind some simple, high level APIs. This enables you to add single sign-on (SSO) features easily to your Teams application.
+Microsoft Teams provides a mechanism by which an application can obtain the signed-in Teams user token to access Microsoft Graph (and other APIs). Teams Toolkit facilitates this interaction by abstracting some of the Microsoft Entra ID flows and integrations behind some simple, high level APIs. This enables you to add single sign-on (SSO) features easily to your Teams application.
 
-For a bot application, user can invoke the AAD consent flow to obtain sso token to call Graph and other APIs.
+For a bot application, user can invoke the Microsoft Entra consent flow to obtain sso token to call Graph and other APIs.
 
 <h2>Contents </h2>
 
 - [Changes to your project](#1)
 - [Update code to Use SSO for Bot](#2)
-  - [Set up the AAD redirects](#2.1)
+  - [Set up the Microsoft Entra redirects](#2.1)
   - [Update your business logic](#2.2)
   - [(Optional) Add a new sso command to the bot](#2.3)
 - [Update code to Use SSO for Message Extension](#3)
 - [Debug your application](#4)
-- [Customize AAD applications](#5)
+- [Customize Microsoft Entra applications](#5)
 - [Trouble Shooting](#6)
 
 <h2 id='1'>Changes to your project</h2>
@@ -29,7 +29,7 @@ After you successfully added SSO into your project, Teams Toolkit will create an
 | Modify | `azureWebAppBotConfig.bicep` under `templates/azure/teamsFx` and `azure.parameters.dev.json` under `.fx/configs` | Insert environment variables used for bot web app to enable SSO feature                                                                |
 | Modify | `manifest.template.json` under `templates/appPackage`                                                            | An `webApplicationInfo` object will be added into your Teams app manifest template. This field is required by Teams when enabling SSO. |
 | Modify | `projectSettings.json` under `.fx/configs`                                                                       | Add bot sso capability, which will be used internally by Teams Toolkit.                                                                |
-| Create | `aad.template.json` under `templates/appPackage`                                                                 | The Azure Active Directory application manifest that is used to register the application with AAD.                                     |
+| Create | `aad.template.json` under `templates/appPackage`                                                                 | The Microsoft Entra application manifest that is used to register the application with Microsoft Entra.                                     |
 | Create | `auth/bot`                                                                                                       | Reference code, redirect pages and a `README.md` file. These files are provided for reference. See below for more information.         |
 
 <h2 id='2'>Update your code to Use SSO for Bot</h2>
@@ -38,9 +38,9 @@ As described above, the Teams Toolkit generated some configuration to set up you
 
 > Note: The following part is for `command and response bot`. For `basic bot`, please refer to the [bot-sso sample](https://aka.ms/bot-sso-sample).
 
-<h3 id='2.1'>Set up the AAD redirects</h3>
+<h3 id='2.1'>Set up the Microsoft Entra redirects</h3>
 
-1. Move the `auth/bot/public` folder to `bot/src`. This folder contains HTML pages that the bot application hosts. When single sign-on flows are initiated with AAD, AAD will redirect the user to these pages.
+1. Move the `auth/bot/public` folder to `bot/src`. This folder contains HTML pages that the bot application hosts. When single sign-on flows are initiated with Microsoft Entra, Microsoft Entra will redirect the user to these pages.
 1. Modify your `bot/src/index` to add the appropriate `restify` routes to these pages.
 
    ```ts
@@ -56,7 +56,7 @@ As described above, the Teams Toolkit generated some configuration to set up you
 
 <h3 id='2.2'>Update your business logic</h3>
 
-The sample business logic provides a sso command handler `ProfileSsoCommandHandler` that use an AAD token to call Microsoft Graph. This token is obtained by using the logged-in Teams user token. The flow is brought together in a dialog that will display a consent dialog if required.
+The sample business logic provides a sso command handler `ProfileSsoCommandHandler` that use a Microsoft Entra token to call Microsoft Graph. This token is obtained by using the logged-in Teams user token. The flow is brought together in a dialog that will display a consent dialog if required.
 
 To make this work in your application:
 
@@ -336,7 +336,7 @@ You can update the query logic in the `handleMessageExtensionQueryWithSSO` with
 
 To make this work in your application:
 
-1. Move the `auth/bot/public` folder to `bot`. This folder contains HTML pages that the bot application hosts. When single sign-on flows are initiated with AAD, AAD will redirect the user to these pages.
+1. Move the `auth/bot/public` folder to `bot`. This folder contains HTML pages that the bot application hosts. When single sign-on flows are initiated with Microsoft Entra, Microsoft Entra will redirect the user to these pages.
 1. Modify your `bot/index` to add the appropriate `restify` routes to these pages.
 
    ```ts
@@ -394,17 +394,17 @@ To make this work in your application:
 
 You can debug your application by pressing F5.
 
-Teams Toolkit will use the AAD manifest file to register a AAD application registered for SSO.
+Teams Toolkit will use the Microsoft Entra manifest file to register a Microsoft Entra application registered for SSO.
 
 To learn more about Teams Toolkit local debug functionalities, refer to this [document](https://docs.microsoft.com/microsoftteams/platform/toolkit/debug-local).
 
-<h2 id='5'>Customize AAD applications</h2>
+<h2 id='5'>Customize Microsoft Entra applications</h2>
 
-The AAD [manifest](https://docs.microsoft.com/azure/active-directory/develop/reference-app-manifest) allows you to customize various aspects of your application registration. You can update the manifest as needed.
+The Microsoft Entra [manifest](https://docs.microsoft.com/azure/active-directory/develop/reference-app-manifest) allows you to customize various aspects of your application registration. You can update the manifest as needed.
 
 Follow this [document](https://aka.ms/teamsfx-aad-manifest#customize-aad-manifest-template) if you need to include additional API permissions to access your desired APIs.
 
-Follow this [document](https://aka.ms/teamsfx-aad-manifest#How-to-view-the-AAD-app-on-the-Azure-portal) to view your AAD application in Azure Portal.
+Follow this [document](https://aka.ms/teamsfx-aad-manifest#How-to-view-the-AAD-app-on-the-Azure-portal) to view your Microsoft Entra application in Azure Portal.
 
 <h2 id='6'>Trouble Shooting </h2>
 

package/templates/plugins/resource/aad/auth/bot/README.txt

@@ -1,13 +1,13 @@
 Enable single sign-on for Teams bot applications
 -------------------------
 
-For Teams bot application, SSO manifests as an Adaptive Card which the user can interact with to invoke the AAD consent flow.
+For Teams bot application, SSO manifests as an Adaptive Card which the user can interact with to invoke the Microsoft Entra consent flow.
 
 Files generated/updated in your project
 -------------------------
 
 1. New file - `aad.template.json` is created in folder `templates/appPackage`
-   - The Azure Active Directory application manifest that is used to register the application with AAD.
+   - The Azure Active Directory application manifest that is used to register the application with Microsoft Entra.
 2.  Update file - 'templates/appPackage/manifest.template.json'
    - An `webApplicationInfo` object will be added into your Teams app manifest template. This field is required by Teams when enabling SSO. |
 3. New file - `Auth/bot`
@@ -24,7 +24,7 @@ Note: This part is for `command and response bot`.
    Microsoft.Bot.Builder >= 4.17.1
 
 2. Create "Pages" folder and move files in `Auth/bot/Pages` folder to `Pages`
-   `Auth/bot/Pages` folder contains HTML pages that hosted by bot application. When single sign-on flows are initiated with AAD, AAD will redirect the user to these pages.
+   `Auth/bot/Pages` folder contains HTML pages that hosted by bot application. When single sign-on flows are initiated with Microsoft Entra ID, Microsoft Entra ID will redirect the user to these pages.
 
 3. Create "SSO" folder and move files in 'Auth/bot/SSO' folder to 'SSO'
    This folder contains two files as reference for SSO implementation:
@@ -174,15 +174,15 @@ to install the app to
 3. Press F5, or select the Debug > Start Debugging menu in Visual Studio
 4. In the launched browser, select the Add button to load the app in Teams
 
-Teams Toolkit will use the AAD manifest file to register a AAD application registered for SSO.
+Teams Toolkit will use the Microsoft Entra manifest file to register a Microsoft Entra application registered for SSO.
 
 To learn more about Teams Toolkit local debug functionalities, refer to https://docs.microsoft.com/microsoftteams/platform/toolkit/debug-local.
 
-Customize AAD applications
+Customize Microsoft Entra applications
 -------------------------
-The AAD manifest allows you to customize various aspects of your application registration. You can update the manifest as needed.
+The Microsoft Entra manifest allows you to customize various aspects of your application registration. You can update the manifest as needed.
 Related Doc: https://docs.microsoft.com/azure/active-directory/develop/reference-app-manifest
 
 Follow https://aka.ms/teamsfx-aad-manifest#how-to-customize-the-aad-manifest-template if you need to include additional API permissions to access your desired APIs.
 
-Follow https://aka.ms/teamsfx-aad-manifest#How-to-view-the-AAD-app-on-the-Azure-portal to view your AAD application in Azure Portal.
+Follow https://aka.ms/teamsfx-aad-manifest#How-to-view-the-AAD-app-on-the-Azure-portal to view your Microsoft Entra application in Azure Portal.

package/templates/plugins/resource/aad/auth/bot/csharp/Pages/BotAuthorizeEndPage.cshtml

@@ -1,61 +1,65 @@
 @page "/bot-auth-end.html"
 
 <html>
+
 <head>
-    <title>Login End Page</title>
-    <meta charset="utf-8" />
+  <title>Login End Page</title>
+  <meta charset="utf-8" />
 </head>
 
 <body>
-    <script src="https://res.cdn.office.net/teams-js/2.7.1/js/MicrosoftTeams.min.js" integrity="sha384-4Gy2G+qxzDVdrdemcVqKVQvaSK1Ghg3x6xcsaMLPc/pw7KPtiogHGM97LTWF2PWg" crossorigin="anonymous"></script>
-    <div id="divError"></div>
-    <script type="text/javascript">
-        microsoftTeams.app.initialize().then(()=>{
-          let hashParams = getHashParameters();
-          if (hashParams["error"]) {
-            // Authentication failed
-            handleAuthError(hashParams["error"], hashParams);
-          } else if (hashParams["code"]) {
-            // Get the stored state parameter and compare with incoming state
-            let expectedState = localStorage.getItem("state");
-            if (expectedState !== hashParams["state"]) {
-              // State does not match, report error
-              handleAuthError("StateDoesNotMatch", hashParams);
-            } else {
-              microsoftTeams.authentication.notifySuccess();
-            }
-          } else {
-            // Unexpected condition: hash does not contain error or access_token parameter
-            handleAuthError("UnexpectedFailure", hashParams);
-          }
-        });
-        
-        // Parse hash parameters into key-value pairs
-        function getHashParameters() {
-          let hashParams = {};
-          location.hash
-            .substr(1)
-            .split("&")
-            .forEach(function (item) {
-              let s = item.split("="),
-                k = s[0],
-                v = s[1] && decodeURIComponent(s[1]);
-              hashParams[k] = v;
-            });
-          return hashParams;
-        }
-        // Show error information
-        function handleAuthError(errorType, errorMessage) {
-          const err = JSON.stringify({
-            error: errorType,
-            message: JSON.stringify(errorMessage),
-          });
-          let para = document.createElement("p");
-          let node = document.createTextNode(err);
-          para.appendChild(node);
-          let element = document.getElementById("divError");
-          element.appendChild(para);
+  <script src="https://res.cdn.office.net/teams-js/2.17.0/js/MicrosoftTeams.min.js"
+    integrity="sha384-xp55t/129OsN192JZYLP0rGhzjCF9aYtjY0LVtXvolkDrBe4Jchylp56NrUYJ4S2"
+    crossorigin="anonymous"></script>
+  <div id="divError"></div>
+  <script type="text/javascript">
+    microsoftTeams.app.initialize().then(() => {
+      let hashParams = getHashParameters();
+      if (hashParams["error"]) {
+        // Authentication failed
+        handleAuthError(hashParams["error"], hashParams);
+      } else if (hashParams["code"]) {
+        // Get the stored state parameter and compare with incoming state
+        let expectedState = localStorage.getItem("state");
+        if (expectedState !== hashParams["state"]) {
+          // State does not match, report error
+          handleAuthError("StateDoesNotMatch", hashParams);
+        } else {
+          microsoftTeams.authentication.notifySuccess();
         }
-    </script>
+      } else {
+        // Unexpected condition: hash does not contain error or access_token parameter
+        handleAuthError("UnexpectedFailure", hashParams);
+      }
+    });
+
+    // Parse hash parameters into key-value pairs
+    function getHashParameters() {
+      let hashParams = {};
+      location.hash
+        .substr(1)
+        .split("&")
+        .forEach(function (item) {
+          let s = item.split("="),
+            k = s[0],
+            v = s[1] && decodeURIComponent(s[1]);
+          hashParams[k] = v;
+        });
+      return hashParams;
+    }
+    // Show error information
+    function handleAuthError(errorType, errorMessage) {
+      const err = JSON.stringify({
+        error: errorType,
+        message: JSON.stringify(errorMessage),
+      });
+      let para = document.createElement("p");
+      let node = document.createTextNode(err);
+      para.appendChild(node);
+      let element = document.getElementById("divError");
+      element.appendChild(para);
+    }
+  </script>
 </body>
+
 </html>

package/templates/plugins/resource/aad/auth/bot/js/public/auth-end.html

@@ -8,7 +8,11 @@
   </head>
 
   <body>
-    <script src="https://res.cdn.office.net/teams-js/2.7.1/js/MicrosoftTeams.min.js" integrity="sha384-4Gy2G+qxzDVdrdemcVqKVQvaSK1Ghg3x6xcsaMLPc/pw7KPtiogHGM97LTWF2PWg" crossorigin="anonymous"></script>
+    <script
+      src="https://res.cdn.office.net/teams-js/2.17.0/js/MicrosoftTeams.min.js"
+      integrity="sha384-xp55t/129OsN192JZYLP0rGhzjCF9aYtjY0LVtXvolkDrBe4Jchylp56NrUYJ4S2"
+      crossorigin="anonymous"
+    ></script>
     <div id="divError"></div>
     <script type="text/javascript">
       microsoftTeams.app.initialize().then(() => {
@@ -31,7 +35,7 @@
           handleAuthError("UnexpectedFailure", hashParams);
         }
       });
-      
+
       // Parse hash parameters into key-value pairs
       function getHashParameters() {
         let hashParams = new Map();

package/templates/plugins/resource/aad/auth/bot/ts/public/auth-end.html

@@ -8,7 +8,11 @@
   </head>
 
   <body>
-    <script src="https://res.cdn.office.net/teams-js/2.7.1/js/MicrosoftTeams.min.js" integrity="sha384-4Gy2G+qxzDVdrdemcVqKVQvaSK1Ghg3x6xcsaMLPc/pw7KPtiogHGM97LTWF2PWg" crossorigin="anonymous"></script>
+    <script
+      src="https://res.cdn.office.net/teams-js/2.17.0/js/MicrosoftTeams.min.js"
+      integrity="sha384-xp55t/129OsN192JZYLP0rGhzjCF9aYtjY0LVtXvolkDrBe4Jchylp56NrUYJ4S2"
+      crossorigin="anonymous"
+    ></script>
     <div id="divError"></div>
     <script type="text/javascript">
       microsoftTeams.app.initialize().then(() => {

package/templates/plugins/resource/aad/auth/tab/README.md

@@ -1,6 +1,6 @@
 # Enable single sign-on for tab applications
 
-Microsoft Teams provides a mechanism by which an application can obtain the signed-in Teams user token to access Microsoft Graph (and other APIs). Teams Toolkit facilitates this interaction by abstracting some of the Azure Active Directory flows and integrations behind some simple, high level APIs. This enables you to add single sign-on (SSO) features easily to your Teams application.
+Microsoft Teams provides a mechanism by which an application can obtain the signed-in Teams user token to access Microsoft Graph (and other APIs). Teams Toolkit facilitates this interaction by abstracting some of the Microsoft Entra flows and integrations behind some simple, high level APIs. This enables you to add single sign-on (SSO) features easily to your Teams application.
 
 # Changes to your project
 
@@ -10,7 +10,7 @@ After you successfully added SSO into your project, Teams Toolkit will create an
 
 | Action | File | Description |
 | - | - | - |
-| Create| `aad.template.json` under `templates/appPackage` | The Azure Active Directory application manifest that is used to register the application with AAD. |
+| Create| `aad.template.json` under `templates/appPackage` | The Microsoft Entra application manifest that is used to register the application with Microsoft Entra. |
 | Modify | `manifest.template.json` under `templates/appPackage` | An `webApplicationInfo` object will be added into your Teams app manifest template. This field is required by Teams when enabling SSO. |
 | Create | `auth/tab` | Reference code, redirect pages and a `README.md` file. These files are provided for reference. See below for more information. |
 
@@ -37,14 +37,14 @@ These two HTML files are used for auth redirects.
 
 You can debug your application by pressing F5.
 
-Teams Toolkit will use the AAD manifest file to register a AAD application registered for SSO.
+Teams Toolkit will use the Microsoft Entra manifest file to register a Microsoft Entra application registered for SSO.
 
 To learn more about Teams Toolkit local debug functionalities, refer to this [document](https://docs.microsoft.com/microsoftteams/platform/toolkit/debug-local).
 
-# Customize AAD applications
+# Customize Microsoft Entra applications
 
-The AAD [manifest](https://docs.microsoft.com/azure/active-directory/develop/reference-app-manifest) allows you to customize various aspects of your application registration. You can update the manifest as needed.
+The Microsoft Entra [manifest](https://docs.microsoft.com/azure/active-directory/develop/reference-app-manifest) allows you to customize various aspects of your application registration. You can update the manifest as needed.
 
 Follow this [document](https://aka.ms/teamsfx-aad-manifest#how-to-customize-the-aad-manifest-template) if you need to include additional API permissions to access your desired APIs.
 
-Follow this [document](https://aka.ms/teamsfx-aad-manifest#How-to-view-the-AAD-app-on-the-Azure-portal) to view your AAD application in Azure Portal.
+Follow this [document](https://aka.ms/teamsfx-aad-manifest#How-to-view-the-AAD-app-on-the-Azure-portal) to view your Microsoft Entra application in Azure Portal.

package/templates/plugins/resource/aad/auth/tab/README.txt

@@ -5,7 +5,7 @@ Files generated/updated in your project
 -------------------------
 
 1. New file - 'aad.template.json' is created in folder 'templates/appPackage'
-   - The Azure Active Directory application manifest that is used to register the application with AAD.
+   - The Microsoft Entra application manifest that is used to register the application with Microsoft Entra.
 2. Update file - 'templates/appPackage/manifest.template.json'
    - An 'webApplicationInfo' object will be added into your Teams app manifest template. This field is required by Teams when enabling SSO.
 3. New file - 'Auth/tab'
@@ -31,15 +31,15 @@ to install the app to
 3. Press F5, or select the Debug > Start Debugging menu in Visual Studio
 4. In the launched browser, select the Add button to load the app in Teams
 
-Teams Toolkit will use the AAD manifest file to register a AAD application registered for SSO.
+Teams Toolkit will use the Microsoft Entra manifest file to register a Microsoft Entra application registered for SSO.
 
 To learn more about Teams Toolkit local debug functionalities, refer to https://docs.microsoft.com/microsoftteams/platform/toolkit/debug-local.
 
-Customize AAD applications
+Customize Microsoft Entra applications
 -------------------------
-The AAD manifest allows you to customize various aspects of your application registration. You can update the manifest as needed.
+The Microsoft Entra manifest allows you to customize various aspects of your application registration. You can update the manifest as needed.
 Related Doc: https://docs.microsoft.com/azure/active-directory/develop/reference-app-manifest
 
 Follow https://aka.ms/teamsfx-aad-manifest#how-to-customize-the-aad-manifest-template if you need to include additional API permissions to access your desired APIs.
 
-Follow https://aka.ms/teamsfx-aad-manifest#How-to-view-the-AAD-app-on-the-Azure-portal to view your AAD application in Azure Portal.
+Follow https://aka.ms/teamsfx-aad-manifest#How-to-view-the-AAD-app-on-the-Azure-portal to view your Microsoft Entra application in Azure Portal.

package/templates/plugins/resource/aad/auth/tab/js/public/auth-end.html

@@ -7,13 +7,17 @@
   </head>
 
   <body>
-  <script src="https://res.cdn.office.net/teams-js/2.7.1/js/MicrosoftTeams.min.js" integrity="sha384-4Gy2G+qxzDVdrdemcVqKVQvaSK1Ghg3x6xcsaMLPc/pw7KPtiogHGM97LTWF2PWg" crossorigin="anonymous"></script>
+    <script
+      src="https://res.cdn.office.net/teams-js/2.17.0/js/MicrosoftTeams.min.js"
+      integrity="sha384-xp55t/129OsN192JZYLP0rGhzjCF9aYtjY0LVtXvolkDrBe4Jchylp56NrUYJ4S2"
+      crossorigin="anonymous"
+    ></script>
     <script
       type="text/javascript"
       src="https://alcdn.msauth.net/browser/2.21.0/js/msal-browser.min.js"
       integrity="sha384-s/NxjjAgw1QgpDhOlVjTceLl4axrp5nqpUbCPOEQy1PqbFit9On6uw2XmEF1eq0s"
-      crossorigin="anonymous">
-    </script>
+      crossorigin="anonymous"
+    ></script>
     <script type="text/javascript">
       var currentURL = new URL(window.location);
       var clientId = currentURL.searchParams.get("clientId");
@@ -24,20 +28,23 @@
             auth: {
               clientId: clientId,
               authority: `https://login.microsoftonline.com/${context.user.tenant.id}`,
-              navigateToLoginRequestUrl: false
+              navigateToLoginRequestUrl: false,
             },
             cache: {
               cacheLocation: "sessionStorage",
             },
-          }
+          };
 
           const msalInstance = new window.msal.PublicClientApplication(msalConfig);
-          msalInstance.handleRedirectPromise()
+          msalInstance
+            .handleRedirectPromise()
             .then((tokenResponse) => {
               if (tokenResponse !== null) {
-                microsoftTeams.authentication.notifySuccess(JSON.stringify({
-                  sessionStorage: sessionStorage
-                }));
+                microsoftTeams.authentication.notifySuccess(
+                  JSON.stringify({
+                    sessionStorage: sessionStorage,
+                  })
+                );
               } else {
                 microsoftTeams.authentication.notifyFailure("Get empty response.");
               }

package/templates/plugins/resource/aad/auth/tab/js/public/auth-start.html

@@ -7,13 +7,17 @@
   </head>
 
   <body>
-  <script src="https://res.cdn.office.net/teams-js/2.7.1/js/MicrosoftTeams.min.js" integrity="sha384-4Gy2G+qxzDVdrdemcVqKVQvaSK1Ghg3x6xcsaMLPc/pw7KPtiogHGM97LTWF2PWg" crossorigin="anonymous"></script>
+    <script
+      src="https://res.cdn.office.net/teams-js/2.17.0/js/MicrosoftTeams.min.js"
+      integrity="sha384-xp55t/129OsN192JZYLP0rGhzjCF9aYtjY0LVtXvolkDrBe4Jchylp56NrUYJ4S2"
+      crossorigin="anonymous"
+    ></script>
     <script
       type="text/javascript"
       src="https://alcdn.msauth.net/browser/2.21.0/js/msal-browser.min.js"
       integrity="sha384-s/NxjjAgw1QgpDhOlVjTceLl4axrp5nqpUbCPOEQy1PqbFit9On6uw2XmEF1eq0s"
-      crossorigin="anonymous">
-    </script>
+      crossorigin="anonymous"
+    ></script>
     <script type="text/javascript">
       microsoftTeams.app.initialize().then(() => {
         microsoftTeams.app.getContext().then(async (context) => {
@@ -27,23 +31,23 @@
             auth: {
               clientId: clientId,
               authority: `https://login.microsoftonline.com/${context.user.tenant.id}`,
-              navigateToLoginRequestUrl: false
+              navigateToLoginRequestUrl: false,
             },
             cache: {
               cacheLocation: "sessionStorage",
             },
-          }
+          };
 
           const msalInstance = new msal.PublicClientApplication(msalConfig);
           const scopesArray = scope.split(" ");
           const scopesRequest = {
             scopes: scopesArray,
             redirectUri: window.location.origin + `/auth-end.html?clientId=${clientId}`,
-            loginHint: loginHint
+            loginHint: loginHint,
           };
           await msalInstance.loginRedirect(scopesRequest);
         });
       });
-      </script>
+    </script>
   </body>
 </html>

package/templates/plugins/resource/aad/auth/tab/js/sso/GetUserProfile.jsx

@@ -27,7 +27,7 @@ export function GetUserProfile(props) {
       // }
       return { profile };
     },
-    // Add scope for your Azure AD app. For example: Mail.Read, etc.
+    // Add scope for your Microsoft Entra app. For example: Mail.Read, etc.
     // Use teamsfx instance from `InitTeamsFx`
     { scope: ["User.Read"], teamsfx: teamsfx }
   );

package/templates/plugins/resource/aad/auth/tab/ts/public/auth-end.html

@@ -7,13 +7,17 @@
   </head>
 
   <body>
-  <script src="https://res.cdn.office.net/teams-js/2.7.1/js/MicrosoftTeams.min.js" integrity="sha384-4Gy2G+qxzDVdrdemcVqKVQvaSK1Ghg3x6xcsaMLPc/pw7KPtiogHGM97LTWF2PWg" crossorigin="anonymous"></script>
+    <script
+      src="https://res.cdn.office.net/teams-js/2.17.0/js/MicrosoftTeams.min.js"
+      integrity="sha384-xp55t/129OsN192JZYLP0rGhzjCF9aYtjY0LVtXvolkDrBe4Jchylp56NrUYJ4S2"
+      crossorigin="anonymous"
+    ></script>
     <script
       type="text/javascript"
       src="https://alcdn.msauth.net/browser/2.21.0/js/msal-browser.min.js"
       integrity="sha384-s/NxjjAgw1QgpDhOlVjTceLl4axrp5nqpUbCPOEQy1PqbFit9On6uw2XmEF1eq0s"
-      crossorigin="anonymous">
-    </script>
+      crossorigin="anonymous"
+    ></script>
     <script type="text/javascript">
       var currentURL = new URL(window.location);
       var clientId = currentURL.searchParams.get("clientId");
@@ -24,20 +28,23 @@
             auth: {
               clientId: clientId,
               authority: `https://login.microsoftonline.com/${context.user.tenant.id}`,
-              navigateToLoginRequestUrl: false
+              navigateToLoginRequestUrl: false,
             },
             cache: {
               cacheLocation: "sessionStorage",
             },
-          }
+          };
 
           const msalInstance = new window.msal.PublicClientApplication(msalConfig);
-          msalInstance.handleRedirectPromise()
+          msalInstance
+            .handleRedirectPromise()
             .then((tokenResponse) => {
               if (tokenResponse !== null) {
-                microsoftTeams.authentication.notifySuccess(JSON.stringify({
-                  sessionStorage: sessionStorage
-                }));
+                microsoftTeams.authentication.notifySuccess(
+                  JSON.stringify({
+                    sessionStorage: sessionStorage,
+                  })
+                );
               } else {
                 microsoftTeams.authentication.notifyFailure("Get empty response.");
               }

package/templates/plugins/resource/aad/auth/tab/ts/public/auth-start.html

@@ -7,13 +7,17 @@
   </head>
 
   <body>
-  <script src="https://res.cdn.office.net/teams-js/2.7.1/js/MicrosoftTeams.min.js" integrity="sha384-4Gy2G+qxzDVdrdemcVqKVQvaSK1Ghg3x6xcsaMLPc/pw7KPtiogHGM97LTWF2PWg" crossorigin="anonymous"></script>
+    <script
+      src="https://res.cdn.office.net/teams-js/2.17.0/js/MicrosoftTeams.min.js"
+      integrity="sha384-xp55t/129OsN192JZYLP0rGhzjCF9aYtjY0LVtXvolkDrBe4Jchylp56NrUYJ4S2"
+      crossorigin="anonymous"
+    ></script>
     <script
       type="text/javascript"
       src="https://alcdn.msauth.net/browser/2.21.0/js/msal-browser.min.js"
       integrity="sha384-s/NxjjAgw1QgpDhOlVjTceLl4axrp5nqpUbCPOEQy1PqbFit9On6uw2XmEF1eq0s"
-      crossorigin="anonymous">
-    </script>
+      crossorigin="anonymous"
+    ></script>
     <script type="text/javascript">
       microsoftTeams.app.initialize().then(() => {
         microsoftTeams.app.getContext().then(async (context) => {
@@ -27,23 +31,23 @@
             auth: {
               clientId: clientId,
               authority: `https://login.microsoftonline.com/${context.user.tenant.id}`,
-              navigateToLoginRequestUrl: false
+              navigateToLoginRequestUrl: false,
             },
             cache: {
               cacheLocation: "sessionStorage",
             },
-          }
+          };
 
           const msalInstance = new msal.PublicClientApplication(msalConfig);
           const scopesArray = scope.split(" ");
           const scopesRequest = {
             scopes: scopesArray,
             redirectUri: window.location.origin + `/auth-end.html?clientId=${clientId}`,
-            loginHint: loginHint
+            loginHint: loginHint,
           };
           await msalInstance.loginRedirect(scopesRequest);
         });
       });
-      </script>
+    </script>
   </body>
 </html>

package/templates/plugins/resource/aad/auth/tab/ts/sso/GetUserProfile.tsx

@@ -28,7 +28,7 @@ export function GetUserProfile(props: { teamsfx?: TeamsFx }) {
       // }
       return { profile };
     },
-    // Add scope for your Azure AD app. For example: Mail.Read, etc.
+    // Add scope for your Microsoft Entra app. For example: Mail.Read, etc.
     // Use teamsfx instance from `InitTeamsFx`
     { scope: ["User.Read"], teamsfx: teamsfx }
   );