From c4f5dc89d2a2200fd71eb89b8f0326b8442f697c Mon Sep 17 00:00:00 2001
From: TimShererWithAquent
 <28902327+TimShererWithAquent@users.noreply.github.com>
Date: Wed, 20 Mar 2024 09:19:44 -0700
Subject: [PATCH] Add deprecation note.

---
 .../v1.0/resources/authenticationmethods-overview.md          | 4 +++-
 concepts/auth-cloudsolutionprovider.md                        | 4 +++-
 2 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/api-reference/v1.0/resources/authenticationmethods-overview.md b/api-reference/v1.0/resources/authenticationmethods-overview.md
index f8816889b52..888b38fd961 100644
--- a/api-reference/v1.0/resources/authenticationmethods-overview.md
+++ b/api-reference/v1.0/resources/authenticationmethods-overview.md
@@ -2,7 +2,7 @@
 title: "Microsoft Entra authentication methods API overview"
 description: "Authentication methods are how users authenticate in Azure AD."
 ms.localizationpriority: medium
-ms.custom: has-azure-ad-ps-ref
+ms.custom: has-azure-ad-ps-ref, azure-ad-ref-level-one-done
 author: "jpettere"
 ms.reviewer: intelligentaccesspm
 ms.subservice: "entra-sign-in"
@@ -50,6 +50,8 @@ The following authentication methods are not yet supported in Microsoft Graph v1
 |Hardware token | Allow users to perform multifactor authentication using a physical device that provides a one-time code. | Get a hardware token assigned to a user.|
 |Security questions and answers | Allow users to validate their identity when performing a self-service password reset. |Delete a security question a user registered.|
 
+[!INCLUDE [Azure AD PowerShell deprecation note](~/../api-reference/reusable-content/msgraph-powershell/includes/aad-powershell-deprecation-note.md)]
+
 ## Require re-register multifactor authentication
 
 To require users to set up a new multifactor authentication the next time they sign in, call the individual DELETE authentication method operations to delete each of the user's current authentication methods. After the user has no more methods, they're prompted to register the next time they sign in where strong authentication is required.
diff --git a/concepts/auth-cloudsolutionprovider.md b/concepts/auth-cloudsolutionprovider.md
index 0154aa535a4..62e4535ea95 100644
--- a/concepts/auth-cloudsolutionprovider.md
+++ b/concepts/auth-cloudsolutionprovider.md
@@ -4,7 +4,7 @@ description: "This article describes how to enable application access to partner
 author: koravvams
 ms.localizationpriority: high
 ms.subservice: "partner-customer-administration"
-ms.custom: graphiamtop20, has-azure-ad-ps-ref
+ms.custom: graphiamtop20, has-azure-ad-ps-ref, azure-ad-ref-level-one-done
 ---
 
 # Call Microsoft Graph from a Cloud Solution Provider application
@@ -40,6 +40,8 @@ The initial steps required here follow most of the same steps used to register a
 
 Finally grant your partner-managed app those configured permissions for all your customers. You can do this by adding the **servicePrincipal** that represents the app to the *Adminagents* group in your Partner tenant, using [Azure AD PowerShell V2](https://www.powershellgallery.com/packages/AzureAD) or [Microsoft Graph PowerShell](/powershell/microsoftgraph/installation). Follow these steps to find the *Adminagents* group, the **servicePrincipal** and add it to the group.
 
+[!INCLUDE [Azure AD PowerShell deprecation note](~/../api-reference/reusable-content/msgraph-powershell/includes/aad-powershell-deprecation-note.md)]
+
 # [Azure AD PowerShell](#tab/azuread)
 
 1. Open a PowerShell session and connect to your partner tenant by entering your admin credentials into the sign-in window.