Merge pull request #184328 from pamistel/pamistel_authenticationFix

Moved warning banner up

Author: PMEds28

articles/spatial-anchors/concepts/authentication.md

@@ -15,6 +15,9 @@ ms.custom: devx-track-csharp, subject-rbac-steps
 
 In this article, you'll learn the various ways you can authenticate to Azure Spatial Anchors from your app or web service. You'll also learn about the ways you can use Azure role-based access control (Azure RBAC) in Azure Active Directory (Azure AD) to control access to your Spatial Anchors accounts.
 
+> [!WARNING]
+> We recommend that you use account keys for quick onboarding, but only during development/prototyping. We don't recommend that you ship your application to production with an embedded account key in it. Instead, use the user-based or service-based Azure AD authentication approaches described next.
+
 ## Overview
 
 ![Diagram that shows an overview of authentication to Azure Spatial Anchors.](./media/spatial-anchors-authentication-overview.png)
@@ -82,9 +85,6 @@ configuration.AccountKey(LR"(MyAccountKey)");
 
 After you set that property, the SDK will handle the exchange of the account key for an access token and the necessary caching of tokens for your app.
 
-> [!WARNING]
-> We recommend that you use account keys for quick onboarding, but only during development/prototyping. We don't recommend that you ship your application to production with an embedded account key in it. Instead, use the user-based or service-based Azure AD authentication approaches described next.
-
 ## Azure AD user authentication
 
 For applications that target Azure Active Directory users, we recommend that you use an Azure AD token for the user. You can obtain this token by using the [MSAL](../../active-directory/develop/msal-overview.md). Follow the steps in the [quickstart on registering an app](../../active-directory/develop/quickstart-register-app.md), which include: