Fix links in other docs

Author: rolyon

articles/automation/automation-security-overview.md

@@ -63,7 +63,7 @@ You need the `Microsoft.Authorization/*/Write` permission. This permission is ob
 - [Owner](../role-based-access-control/built-in-roles.md#owner)
 - [User Access Administrator](../role-based-access-control/built-in-roles.md#user-access-administrator)
 
-To learn more about classic subscription permissions, see [Azure classic subscription administrators](../role-based-access-control/classic-administrators.md#add-a-co-administrator).
+To learn more about classic subscription permissions, see [Azure classic subscription administrators](../role-based-access-control/classic-administrators.md).
 
 <a name='azure-ad-permissions'></a>
 

articles/cost-management-billing/manage/cancel-azure-subscription.md

@@ -59,7 +59,7 @@ The following table describes the permission required to cancel a subscription.
 |[Microsoft Enterprise Agreement](https://azure.microsoft.com/pricing/enterprise-agreement/) and [Enterprise Dev/Test](https://azure.microsoft.com/offers/ms-azr-0148p/)     |  Service administrator and subscription owner       |
 |[Azure plan](https://azure.microsoft.com/offers/ms-azr-0017g/) and [Azure plan for DevTest](https://azure.microsoft.com/offers/ms-azr-0148g/)     |  Subscription owners      |
 
-An account administrator without the service administrator or subscription owner role can’t cancel an Azure subscription. However, an account administrator can make themself the service administrator and then they can cancel a subscription. For more information, see [Change the Service Administrator](../../role-based-access-control/classic-administrators.md#change-the-service-administrator).
+An account administrator without the service administrator or subscription owner role can’t cancel an Azure subscription. For more information, see [Azure classic subscription administrators](../../role-based-access-control/classic-administrators.md).
 
 ## Cancel a subscription in the Azure portal
 

articles/cost-management-billing/manage/classic-administrator-retire.md

@@ -24,7 +24,7 @@ On August 31, 2024 and later:
 
 - When you create an Azure subscription, the classic Service Administrator role isn't assigned to the subscription. Instead, the user creating the subscription is assigned the Azure RBAC [Owner](../../role-based-access-control/built-in-roles.md#owner) role.
 - During the [Azure subscription Change Directory operation](/entra/fundamentals/how-subscriptions-associated-directory#associate-a-subscription-to-a-directory), the user isn't assigned the Service Administrator role. Instead, the user completing the Change Directory action is assigned the Azure RBAC [Owner](../../role-based-access-control/built-in-roles.md#owner) role.
-- For situations that require changing or removing Service Administrators, ensure that the subscription has Azure RBAC owners assigned on it. If you're a subscription Azure RBAC owner, you can remove the current Service administrator using the information at [Remove the Service Administrator](../../role-based-access-control/classic-administrators.md?tabs=azure-portal#remove-the-service-administrator). If you aren't a subscription RBAC owner, ask your subscription Azure RBAC owner or a global administrator to update or remove the intended service administrator on the subscription. Or, you can ask them to give you an Azure RBAC role so that you can update or remove the Service Administrator.
+- For situations that require changing or removing Service Administrators, ensure that the subscription has Azure RBAC owners assigned on it. If you're a subscription Azure RBAC owner, you can remove the current Service administrator using the information at [Service Administrator retirement](../../role-based-access-control/classic-administrators.md#service-administrator-retirement). If you aren't a subscription RBAC owner, ask your subscription Azure RBAC owner or a global administrator to update or remove the intended service administrator on the subscription. Or, you can ask them to give you an Azure RBAC role so that you can update or remove the Service Administrator.
 
 ## Help and support
 

articles/role-based-access-control/classic-administrators.md

@@ -18,7 +18,7 @@ ms.reviewer: bagovind
 
 Microsoft recommends that you manage access to Azure resources using Azure role-based access control (Azure RBAC). If you're still using the classic deployment model, you'll need to migrate your resources from classic deployment to Resource Manager deployment. For more information, see [Azure Resource Manager vs. classic deployment](../azure-resource-manager/management/deployment-models.md).
 
- If you still have active Co-Administrator or Service Administrator role assignments, convert these roles to Azure RBAC immediately. This article describes the retirement of the Co-Administrator and Service Administrator roles and how to convert these role assignments.
+If you still have active Co-Administrator or Service Administrator role assignments, convert these roles to Azure RBAC immediately. This article describes the retirement of the Co-Administrator and Service Administrator roles and how to convert these role assignments.
 
 ## Frequently asked questions
 

articles/role-based-access-control/rbac-and-directory-admin-roles.md

@@ -94,7 +94,9 @@ Several Microsoft Entra roles span Microsoft Entra ID and Microsoft 365, such as
 ## Classic subscription administrator roles
 
 > [!IMPORTANT]
-> Classic resources and classic administrators will be [retired on August 31, 2024](https://azure.microsoft.com/updates/cloud-services-retirement-announcement/). Starting April 3, 2024, you won't be able to add new Co-Administrators. This date was recently extended. Remove unnecessary Co-Administrators and use Azure RBAC for fine-grained access control.
+> As of **August 31, 2024**, Azure classic administrator roles (along with Azure classic resources and Azure Service Manager) are retired and no longer supported.
+>
+> For more information, see [Azure classic subscription administrators](classic-administrators.md).
 
 Account Administrator, Service Administrator, and Co-Administrator are the three classic subscription administrator roles in Azure. Classic subscription administrators have full access to the Azure subscription. They can manage resources using the Azure portal, Azure Resource Manager APIs, and the classic deployment model APIs. The account that is used to sign up for Azure is automatically set as both the Account Administrator and Service Administrator. Then, additional Co-Administrators can be added. The Service Administrator and the Co-Administrators have the equivalent access of users who have been assigned the Owner role (an Azure role) at the subscription scope. The following table describes the differences between these three classic subscription administrative roles.
 

articles/role-based-access-control/troubleshooting.md

@@ -610,7 +610,7 @@ If you're a Microsoft Entra Global Administrator and you don't have access to a
 ## Classic subscription administrators
 
 > [!IMPORTANT]
-> Classic resources and classic administrators will be [retired on August 31, 2024](https://azure.microsoft.com/updates/cloud-services-retirement-announcement/). Starting April 3, 2024, you won't be able to add new Co-Administrators. This date was recently extended. Remove unnecessary Co-Administrators and use Azure RBAC for fine-grained access control.
+> As of **August 31, 2024**, Azure classic administrator roles (along with Azure classic resources and Azure Service Manager) are retired and no longer supported.
 >
 > For more information, see [Azure classic subscription administrators](classic-administrators.md).