Merge pull request #114187 from mmacy/msid-converged-app-cleanse

[msid][ocv] converged application clarification

Author: garycentric

articles/active-directory/develop/app-registration-portal-training-guide.md

@@ -18,7 +18,7 @@ ms.custom: aaddev
 
 # The new Azure portal app registration experience
 
-There are many improvements in the new [App registrations](https://go.microsoft.com/fwlink/?linkid=2083908) experience in the Azure portal. If you're more familiar with the Application registration portal (apps.dev.microsoft.com) experience for registering or managing converged applications, referred to as the old experience, this training guide will get you started using the new experience.
+There are many improvements in the new [App registrations](https://go.microsoft.com/fwlink/?linkid=2083908) experience in the Azure portal. If you're more familiar with the Application registration portal (apps.dev.microsoft.com) for registering or managing applications, referred to here as the "old experience," this guide will get you started using the new experience.
 
 ## What's not changing?
 
@@ -41,8 +41,8 @@ There are many improvements in the new [App registrations](https://go.microsoft.
 
 ## Key changes
 
--   In the old experience, apps were by default registered as converged
-    apps supporting all organizational accounts (multitenant) as well as
+-   In the old experience, apps were by default registered as *converged*
+    apps - apps that support all organizational accounts (multitenant) as well as
     personal Microsoft accounts. This could not be modified through the
     old experience, making it difficult to create apps that supported
     only organizational accounts (either multitenant or single tenant).
@@ -75,10 +75,10 @@ There are many improvements in the new [App registrations](https://go.microsoft.
 
 ## New app registration
 
-In the old experience, to register a converged app you were only
+In the old experience, to register an app you were only
 required to provide a Name. The apps that were created were registered
-as converged apps supporting all organizational directory (multitenant)
-as well as personal Microsoft accounts.  This could not be modified through the old experience, making it difficult to create apps that supported only organizational accounts (either multitenant or single tenant). [Learn more about supported account types](v2-supported-account-types.md)
+as *converged* apps - apps supporting all organizational directories (multitenant)
+as well as personal Microsoft accounts.  This could not be modified through the old experience, making it difficult to create apps that supported only organizational accounts (either single- or multi-tenant). [Learn more about supported account types](v2-supported-account-types.md)
 
 In the new experience, you must provide a Name for the app and choose
 the Supported account types. You can optionally provide a redirect URI.
@@ -89,25 +89,19 @@ quickstart](quickstart-register-app.md).
 
 ## App management page
 
-The old experience had a single app management page for converged apps
+The old experience had a single app management page for apps
 with the following sections: Properties, Application secrets, Platforms,
 Owners, Microsoft Graph Permissions, Profile, and Advanced Options.
 
-The new experience in the Azure portal represents these features into
+The new experience in the Azure portal presents these features in
 separate pages. Here's where you can find the equivalent functionality:
 
--   Properties - Name and Application ID is on the Overview page.
-
--   Application Secrets is on the Certificates & secrets page
-
--   Platforms configuration is on the Authentication page
-
--   Microsoft Graph permissions is on the API permissions page along
-    with other permissions
-
--   Profile is on Branding page
-
--   Advanced option - Live SDK support is on the Authentication page.
+- Properties - Name and Application ID is on the Overview page.
+- Application Secrets is on the Certificates & secrets page
+- Platforms configuration is on the Authentication page
+- Microsoft Graph permissions is on the API permissions page along with other permissions
+- Profile is on Branding page
+- Advanced option - Live SDK support is on the Authentication page.
 
 ## Application secrets/Certificates & secrets
 
@@ -179,7 +173,7 @@ the manifest editor or the API, or didn't exist.
 -   Publisher domain (which is displayed to users on the [application\'s
     consent
     prompt](application-consent-experience.md))
-    can be found on the Branding blade page. For more info on how to
+    can be found on the Branding page. For more info on how to
     configure a publisher domain, see [this
     how-to](howto-configure-publisher-domain.md).
 
@@ -199,3 +193,7 @@ The new experience has the following limitations:
 
    > [!NOTE]
    > If you're a personal Microsoft account user in Azure AD tenant, and the tenant admin has restricted access to Azure portal, you may get an access denied. However, if you come through the shortcut by typing App registrations in the search bar or pinning it, you'll be able to access the new experience.
+
+## Next steps
+
+To get started with the new app registration experience, see [Quickstart: Register an application with the Microsoft identity platform](quickstart-register-app.md).

articles/active-directory/develop/msal-net-token-cache-serialization.md

@@ -48,7 +48,7 @@ The following classes and interfaces are used in token cache serialization:
 
 The strategies are different depending on if you're writing a token cache serialization for a [public client application](msal-client-applications.md) (desktop), or a [confidential client application](msal-client-applications.md)) (web app / web API, daemon app).
 
-### Token cache for a public client 
+### Token cache for a public client
 
 Since MSAL.NET v2.x you have several options for serializing the token cache of a public client. You can serialize the cache only to the MSAL.NET format (the unified format cache is common across MSAL and the platforms).  You can also support the [legacy](https://github.com/AzureAD/azure-activedirectory-library-for-dotnet/wiki/Token-cache-serialization) token cache serialization of ADAL V3.
 
@@ -323,9 +323,10 @@ services.AddDistributedSqlServerCache(options =>
 Their usage is featured in the [ASP.NET Core web app tutorial](https://docs.microsoft.com/aspnet/core/tutorials/first-mvc-app/) in the phase [2-2 Token Cache](https://github.com/Azure-Samples/active-directory-aspnetcore-webapp-openidconnect-v2/tree/master/2-WebApp-graph-user/2-2-TokenCache).
 
 ## Next steps
+
 The following samples illustrate token cache serialization.
 
 | Sample | Platform | Description|
 | ------ | -------- | ----------- |
 |[active-directory-dotnet-desktop-msgraph-v2](https://github.com/azure-samples/active-directory-dotnet-desktop-msgraph-v2) | Desktop (WPF) | Windows Desktop .NET (WPF) application calling the Microsoft Graph API. ![Topology](media/msal-net-token-cache-serialization/topology.png)|
-|[active-directory-dotnet-v1-to-v2](https://github.com/Azure-Samples/active-directory-dotnet-v1-to-v2) | Desktop (Console) | Set of Visual Studio solutions illustrating the migration of Azure AD v1.0 applications (using ADAL.NET) to Azure AD v2.0 applications, also named converged applications (using MSAL.NET), in particular [Token Cache Migration](https://github.com/Azure-Samples/active-directory-dotnet-v1-to-v2/blob/master/TokenCacheMigration/README.md)|
+|[active-directory-dotnet-v1-to-v2](https://github.com/Azure-Samples/active-directory-dotnet-v1-to-v2) | Desktop (Console) | Set of Visual Studio solutions illustrating the migration of Azure AD v1.0 applications (using ADAL.NET) to Microsoft identity platform applications (using MSAL.NET). In particular, see [Token Cache Migration](https://github.com/Azure-Samples/active-directory-dotnet-v1-to-v2/blob/master/TokenCacheMigration/README.md)|

articles/active-directory/develop/registration-config-sso-how-to.md

@@ -7,7 +7,7 @@ manager: CelesteDG
 
 ms.service: active-directory
 ms.subservice: develop
-ms.custom: aaddev 
+ms.custom: aaddev
 ms.workload: identity
 ms.topic: conceptual
 ms.date: 07/15/2019
@@ -37,6 +37,6 @@ For iOS, see [Enabling Cross App SSO in iOS](https://docs.microsoft.com/azure/ac
 
 [Integrating Apps to AzureAD](https://docs.microsoft.com/azure/active-directory/develop/active-directory-integrating-applications)<br>
 
-[Consent and Permissioning for AzureAD v2.0 converged Apps](https://docs.microsoft.com/azure/active-directory/develop/active-directory-v2-scopes)<br>
+[Permissions and consent in the Microsoft identity platform endpoint](https://docs.microsoft.com/azure/active-directory/develop/active-directory-v2-scopes)<br>
 
 [AzureAD StackOverflow](https://stackoverflow.com/questions/tagged/azure-active-directory)