Merge pull request #125425 from ThimoReumerman/patch-1

Update Active Directory to Microsoft Entra at articles/private-link/private-link-service-overview.md

Author: v-dirichards

articles/private-link/private-link-service-overview.md

@@ -2,7 +2,7 @@
 title: What is Azure Private Link service?
 description: Learn about Azure Private Link service.
 services: private-link
-author: abell
+author: AbdullahBell
 ms.service: azure-private-link
 ms.topic: concept-article
 ms.date: 10/15/2024
@@ -67,7 +67,7 @@ A Private Link service specifies the following properties:
 
 - The Private Link Service must be deployed in the same region as the virtual network and the Standard Load Balancer.  
 
-- A single Private Link Service can be accessed from multiple Private Endpoints belonging to different virtual networks, subscriptions and/or Active Directory tenants. The connection is established through a connection workflow. 
+- A single Private Link Service can be accessed from multiple Private Endpoints belonging to different virtual networks, subscriptions and/or Microsoft Entra tenants. The connection is established through a connection workflow. 
 
 - Multiple Private Link services can be created on the same Standard Load Balancer using different front-end IP configurations. There are limits to the number of Private Link services you can create per Standard Load Balancer and per subscription. For details, see [Azure limits](../azure-resource-manager/management/azure-subscription-service-limits.md#networking-limits).
 
@@ -91,7 +91,7 @@ Complete alias:  *Prefix*. {GUID}.*region*.azure.privatelinkservice
 
 The Private Link service provides you with three options in the **Visibility** setting to control the exposure of your service. Your visibility setting determines whether a consumer can connect to your service. Here are the visibility setting options, from most restrictive to least restrictive:
 
-- **Role-based access control only**: If your service is for private consumption from different virtual networks that you own, use role-based access control inside subscriptions that are associated with the same Active Directory tenant. **Cross tenant visibility is permitted through role-based access control**.
+- **Role-based access control only**: If your service is for private consumption from different virtual networks that you own, use role-based access control inside subscriptions that are associated with the same Microsoft Entra tenant. **Cross tenant visibility is permitted through role-based access control**.
 
 - **Restricted by subscription**: If your service will be consumed across different tenants, you can restrict the exposure to a limited set of subscriptions that you trust. Authorizations can be pre-approved.