adding redirect

Author: JimDaly

.openpublishing.redirection.json

@@ -1,6 +1,11 @@
 {
   "redirections": [
-    {
+   {
+      "source_path": "powerapps-docs/developer/data-platform/walkthrough-registering-configuring-simplespa-application-adal-js.md",
+      "redirect_url": "quick-start-register-configure-simplespa-application-msal-js",
+      "redirect_document_id": false
+    }, 
+   {
       "source_path": "powerapps-docs/developer/data-platform/webapi/samples/cdswebapiservice.md",
       "redirect_url": "webapiservice",
       "redirect_document_id": false

powerapps-docs/developer/data-platform/authenticate-oauth.md

@@ -61,10 +61,6 @@ For specific steps to do this, see [Walkthrough: Register an app with Azure Acti
 
 If your app will use Server-to-Server (S2S) authentication, this step is not required. That configuration requires a specific system user and the operations will be performed by that user account rather than any user that must be authenticated.
 
-### Enable Implicit Flow
-
-If you are configuring an app for a Single Page Application (SPA) you must edit the Manifest to set the `oauth2AllowImplicitFlow` value to `true`. More information: [Walkthrough: Registering and configuring a SPA application with adal.js](walkthrough-registering-configuring-simplespa-application-adal-js.md)
-
 ### Use Client Secrets & Certificates
 
 For server to server scenarios there will not be an interactive user account to authenticate. In these cases, you need to provide some means to confirm that the application is trusted. This is done using client secrets or certificates.

powerapps-docs/developer/data-platform/quick-start-register-configure-simplespa-application-msal-js.md

@@ -1,5 +1,5 @@
 ---
-title: "Walkthrough: Registering and configuring a SimpleSPA application with msal.js (Microsoft Dataverse) | Microsoft Docs"
+title: "Quickstart: Register and configure a SPA application for Dataverse using msal.js (Microsoft Dataverse) | Microsoft Docs"
 description: "Describes the process of registering and configuring the simplest Single-Page Application (SPA) to access data in Microsoft Dataverse using msal.js and Cross-origin Resource Sharing (CORS)."
 ms.date: 09/09/2022
 ms.topic: quickstart
@@ -372,7 +372,7 @@ The configured permissions should look like this when you are done:
    > The key difference is the scopes used when getting the access token. You must set the scope to the value of the Dataverse Url + `/.default` or `/user_impersonation`.
    >
    > ```javascript
-   >          // Retrieves top 10 account records from Dataverse
+   >       // Retrieves top 10 account records from Dataverse
    >       function getAccounts(callback) {
    >          // Gets the access token
    >          getTokenPopup({

powerapps-docs/developer/data-platform/walkthrough-register-app-azure-active-directory.md

@@ -80,14 +80,12 @@ This completes the registration of your application in Azure Active Directory.
 
 ## Additional configuration options
 
-If your application will be a Single Page Application (SPA) that depends on CORS you must configure the app registration to support the implicit flow. 
-More information: [Tutorial: Registering and configuring a SPA application with adal.js](walkthrough-registering-configuring-simplespa-application-adal-js.md)
-
 If your application will support server-to-server connections, see [Use Multi-Tenant Server-to-server authentication](use-multi-tenant-server-server-authentication.md)
 
-### See also  
- [Application registration in Azure Active Directory](/azure/active-directory/develop/active-directory-integrating-applications)    
- [Authenticate Users with Dataverse Web Services](authentication.md)
+### See also
+
+[Application registration in Azure Active Directory](/azure/active-directory/develop/active-directory-integrating-applications)<br />
+[Authenticate Users with Dataverse Web Services](authentication.md)
 
 
 [!INCLUDE[footer-include](../../includes/footer-banner.md)]