Update docs for Azure AD product rename (now Microsoft Entra ID) (#1314)

[Azure AD was renamed to Microsoft Entra ID last
year](https://learn.microsoft.com/en-us/entra/fundamentals/new-name#naming-changes-and-exceptions).
This PR updates references in our docs to use the new naming.

In some places you will see existing references to `Entra ID` changed to
`Microsoft Entra ID` to align with Microsoft's branding
([example](https://learn.microsoft.com/en-us/entra/identity/role-based-access-control/permissions-reference#global-administrator:~:text=administrative%20features%20in-,Microsoft%20Entra%20ID,-%2C%20as%20well%20as))
-- the product name is "Microsoft Entra ID" not just "Entra ID".

Please review (somewhat) carefully, this PR was mostly done with `grep`
/ `sed`. I've given it a twice-over to ensure changes make sense in
context.

I have also updated links to Microsoft documentation to use the latest
versions/URLs of reference articles on `learn.microsoft.com`

---------

Co-authored-by: Brian Melton-Grace <[email protected]>
Co-authored-by: Shaquil Hansford <[email protected]>

Author: 3 people

docs/guides/device-gateway/agent.mdx

@@ -25,7 +25,7 @@ This guide will walk you through an example scenario using ngrok to set up a sec
 
 Consider a situation where a network of smart factories is coming online, each with IoT-connected machines, telemetry sensors, and a real-time monitoring dashboard.
 
-In this scenario, each factory's network blocks inbound connections, but the technicians need temporary access to the dashboard. The telemetry API and sensor database must remain permanently accessible from the company's cloud, and access to the dashboard must be authenticated via Azure AD.
+In this scenario, each factory's network blocks inbound connections, but the technicians need temporary access to the dashboard. The telemetry API and sensor database must remain permanently accessible from the company's cloud, and access to the dashboard must be authenticated via Microsoft Entra ID.
 
 Each factory would only need one ngrok agent running.
 

docs/guides/other-guides/security-dev-productivity/security-dev-productivity.md

@@ -80,7 +80,7 @@ ngrok lets you configure authentication in different ways:
 
 ### Enterprise authentication and MFA
 
-Use any OIDC-compliant provider—such as Okta, Microsoft Azure AD or AD
+Use any OIDC-compliant provider—such as Okta, Microsoft Entra ID or AD
 FS, Ping, and Auth0—to control access to public endpoints.
 
 With the [`openid-connect` Traffic Policy
@@ -200,7 +200,7 @@ className="border rounded"
 
 ## Add SSO and MFA to the admin UI
 
-With Dashboard SSO, you can restrict access to the ngrok administrative interface only for users authenticated in your identity providers — such as Okta, Azure AD, Ping, AD FS, and Auth0. The ngrok dashboard SSO works with any SAML provider, and can be used with your identity provider MFA — i.e., Windows Hello, Okta Verify, FIDO, and PingID — to ensure two-factor authentication (2FA) in compliance with your security requirements.
+With Dashboard SSO, you can restrict access to the ngrok administrative interface only for users authenticated in your identity providers — such as Okta, Microsoft Entra ID, Ping, AD FS, and Auth0. The ngrok dashboard SSO works with any SAML provider, and can be used with your identity provider MFA — i.e., Windows Hello, Okta Verify, FIDO, and PingID — to ensure two-factor authentication (2FA) in compliance with your security requirements.
 
 <img
 src={require('./img/mfa-sso.png').default}

docs/iam/sso.mdx

@@ -23,7 +23,7 @@ ngrok supports identity providers which support either SAML or OpenID Connect fo
 SSO including
 [Okta](https://help.okta.com/oie/en-us/Content/Topics/Apps/apps-about-saml.htm)
 and [Microsoft
-AzureAD](https://learn.microsoft.com/en-us/azure/active-directory/fundamentals/auth-saml).
+AzureAD](https://learn.microsoft.com/en-us/entra/architecture/auth-saml).
 
 ## Enforcement
 
@@ -78,7 +78,7 @@ to log in. The description provided when configuring the IdP in your account wil
 ngrok supports a limited subset of [RFC
 7644](https://datatracker.ietf.org/doc/html/rfc7644) to enable SCIM
 provisioning and deprovisioning. ngrok's SCIM implementation works with major
-IdPs like Okta and Azure AD.
+IdPs like Okta and Microsoft Entra ID.
 
 ngrok's SCIM API Base URL is:
 

docs/integrations/azure-ad/index.mdx

@@ -1,12 +1,12 @@
 ---
-name: azure-ad
-title: Azure AD Integration Hub
-sidebar_label: Azure AD
+name: microsoft-entra-id
+title: Microsoft Entra ID Integration Hub
+sidebar_label: Microsoft Entra ID
 description: |
-  Secure access to ngrok tunnels with Azure Active Directory. 
+  Secure access to ngrok tunnels with Microsoft Entra ID. 
   No VPNs, Firewalls, or complex network rules required.
 excerpt: |
-  Secure access to ngrok tunnels with Azure Active Directory.
+  Secure access to ngrok tunnels with Microsoft Entra ID.
 ---
 
 import IntegrationPageList from "@site/src/components/IntegrationPageList";

docs/integrations/azure-ad/k8s.mdx

@@ -2,11 +2,11 @@
 description: Add ingress to any app running in Kubernetes, then restrict access to only users authorized through Microsoft Entra ID, using the ngrok Kubernetes Operator.
 ---
 
-# Ingress to apps secured by Azure AD (Microsoft Entra ID) in Kubernetes
+# Ingress to apps secured by Microsoft Entra ID in Kubernetes
 
 :::tip TL;DR
 
-To use the ngrok Kubernetes Operator with Azure AD (Microsoft Entra ID):
+To use the ngrok Kubernetes Operator with Microsoft Entra ID:
 
 1. [Create a cluster and deploy an example app](#create-cluster-deploy-example-app)
 2. [Add the ngrok Kubernetes Operator](#add-the-ngrok-kubernetes-operator)
@@ -22,18 +22,18 @@ Microsoft Azure Active Directory (AD)—now known as [Microsoft Entra ID](https:
 
 :::note
 
-In October 2023, Microsoft Azure Active Directory (AD) was [renamed Microsoft Entra ID](https://learn.microsoft.com/en-us/entra/fundamentals/new-name) to "communicate the multicloud, multiplatform functionality" and "alleviate confusion with Windows Server Active Directory." This name change changes nothing about the product or its capabilities. We have used **Azure AD** up to this point due to the recency of the change, but will use **Entra ID** for the remainder.
+In October 2023, Azure Active Directory (AD) was [renamed to Microsoft Entra ID](https://learn.microsoft.com/en-us/entra/fundamentals/new-name) to "communicate the multicloud, multiplatform functionality" and "alleviate confusion with Windows Server Active Directory." This name change changes nothing about the product or its capabilities. We have used **Microsoft Entra ID** up to this point due to the recency of the change, but will use **Entra ID** for the remainder.
 
 :::
+b
+The ngrok Kubernetes Operator and Microsoft Entra ID integrate by letting you not only route public traffic to an app deployed on a Kubernetes cluster, but also restrict access only to users who you have authorized through Microsoft Entra ID.
 
-The ngrok Kubernetes Operator and Entra ID integrate by letting you not only route public traffic to an app deployed on a Kubernetes cluster, but also restrict access only to users who you have authorized through Entra ID.
-
-With this guide, you'll (optionally) create a new Kubernetes cluster and example deployment and install the ngrok Kubernetes Operator to securely route traffic through the [ngrok Cloud Edge](https://ngrok.com/product/cloud-edge). You'll then use the ngrok dashboard to enable Security Assertion Markup Language (SAML), using Entra ID as your identity provider, to authorize specific users with a single sign-on experience.
+With this guide, you'll (optionally) create a new Kubernetes cluster and example deployment and install the ngrok Kubernetes Operator to securely route traffic through the [ngrok Cloud Edge](https://ngrok.com/product/cloud-edge). You'll then use the ngrok dashboard to enable Security Assertion Markup Language (SAML), using Microsoft Entra ID as your identity provider, to authorize specific users with a single sign-on experience.
 
 :::caution This tutorial requires:
 
 1. An [ngrok account](https://ngrok.com/signup) at the [**pay-as-you-go** or **custom**](https://ngrok.com/pricing) tiers.
-2. A Microsoft Azure account with access to an existing Entra ID tenant or the ability to create a new tenant with an Entra ID P1 or P2 license.
+2. A Microsoft Azure account with access to an existing Microsoft Entra ID tenant or the ability to create a new tenant with an Microsoft Entra ID P1 or P2 license.
 3. A Kubernetes cluster, either locally or in a public cloud, with an app you'd like to be publicly accessible to specific users.
 
 :::
@@ -154,7 +154,7 @@ Next, you'll configure and deploy the [ngrok Kubernetes Operator](https://github
 
 ## **Step 3**: Update your ngrok Edge to enable SAML {#update-your-ngrok-edge-to-enable-SAML}
 
-Your Kubernetes-based app is now publicly accessible through the ngrok Cloud Edge—to restrict access to only authorized users with proper Entra ID credentials, you first need to enable SAML on your Edge.
+Your Kubernetes-based app is now publicly accessible through the ngrok Cloud Edge—to restrict access to only authorized users with proper Microsoft Entra ID credentials, you first need to enable SAML on your Edge.
 
 1. Navigate to the [**Edges** section](https://dashboard.ngrok.com/edges) of the ngrok dashboard and click on the Edge created by the ngrok Kubernetes Operator. The domain name should match your `NGROK_DOMAIN`, and you should see **Created by kubernetes-ingress-controller** in the edge's description.
 
@@ -176,11 +176,11 @@ Your Kubernetes-based app is now publicly accessible through the ngrok Cloud Edg
 
 With SAML configured on your ngrok Edge, you can now configure Microsoft Entra ID to operate as your identity provider, often called **IdP**.
 
-1. Access your [Entra ID tenant](https://portal.azure.com/#view/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/~/Overview) in the Azure console.
+1. Access your [Microsoft Entra ID tenant](https://portal.azure.com/#view/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/~/Overview) in the Azure console.
 
 1. Click **Enterprise applications** in the left-hand sidebar, then **+ New application**, and finally **+ Create your own application**. Give your app a name—for our example, `online-boutique` will work nicely, and make sure you've selected the **Integrate any other application you don't find in the gallery (Non-gallery)** option.
 
-   ![Create an application on Amazon Entra ID](img/k8s_create-app.png)
+   ![Create an application on Amazon Microsoft Entra ID](img/k8s_create-app.png)
 
 1. Click **Create** to build your enterprise app, which will take you to its Overview dashboard.
 
@@ -196,7 +196,7 @@ With SAML configured on your ngrok Edge, you can now configure Microsoft Entra I
 
 1. In the **SAML Certificates** box, download the **Federation Metadata XML**.
 
-## **Step 5**: Finish adding Entra ID authorization to your ngrok Edge {#finish-adding-entra-ID-authorization-ngrok-edge}
+## **Step 5**: Finish adding Microsoft Entra ID authorization to your ngrok Edge {#finish-adding-entra-ID-authorization-ngrok-edge}
 
 Time to head back to your ngrok dashboard to finish the SAML configuration.
 
@@ -208,23 +208,23 @@ Time to head back to your ngrok dashboard to finish the SAML configuration.
 
 ## **Step 6**: Test authorization to your app using Microsoft Entra ID {#test-authorization-using-microsoft-entra-id}
 
-You've finished integrating the ngrok Kubernetes Operator and Microsoft Entra ID! Your app, whether the Online Boutique used throughout this guide or a custom deployment, is now publicly accessible only to those authorized with their Entra ID credentials. Time to test how it works:
+You've finished integrating the ngrok Kubernetes Operator and Microsoft Entra ID! Your app, whether the Online Boutique used throughout this guide or a custom deployment, is now publicly accessible only to those authorized with their Microsoft Entra ID credentials. Time to test how it works:
 
 1. Open an incognito/private window in your browser, or a different browser than you've used so far, and navigate again to your `NGROK_DOMAIN`. You should see a single sign-on screen from Microsoft.
 
    ![The single sign-on screen from Microsoft](img/k8s_sso-enabled.png)
 
-2. Enter credentials for a Microsoft account you assigned, either as an individual user or a group, to your enterprise application in Entra ID during [step 4](#create-an-enterprise-app).
+2. Enter credentials for a Microsoft account you assigned, either as an individual user or a group, to your enterprise application in Microsoft Entra ID during [step 4](#create-an-enterprise-app).
 
-   Behind the scenes, ngrok requests your identity provider, Microsoft Entra ID, for authentication. Once you sign in, or are already logged in, Entra ID then returns a SAML assertion to ngrok, telling ngrok your authentication is confirmed and you have authorization to access the app.
+   Behind the scenes, ngrok requests your identity provider, Microsoft Entra ID, for authentication. Once you sign in, or are already logged in, Microsoft Entra ID then returns a SAML assertion to ngrok, telling ngrok your authentication is confirmed and you have authorization to access the app.
 
-   Entra ID will then redirect you back to your app!
+   Microsoft Entra ID will then redirect you back to your app!
 
 ## What's next?
 
-You've now integrated the ngrok Kubernetes Operator with Microsoft Entra ID to restrict access to your app to only authenticated users. With ngrok operating as middleware, handling both ingress to your Kubernetes cluster and the handshake with an Entra ID as an identity provider, you can deploy and secure new apps in a multi-cloud environment using your existing Microsoft/Azure identity and access management settings.
+You've now integrated the ngrok Kubernetes Operator with Microsoft Entra ID to restrict access to your app to only authenticated users. With ngrok operating as middleware, handling both ingress to your Kubernetes cluster and the handshake with an Microsoft Entra ID as an identity provider, you can deploy and secure new apps in a multi-cloud environment using your existing Microsoft/Azure identity and access management settings.
 
-From an end user perspective, they only need to sign in once, using their Microsoft credentials, to authenticate themselves and access any number of applications you manage using Entra ID.
+From an end user perspective, they only need to sign in once, using their Microsoft credentials, to authenticate themselves and access any number of applications you manage using Microsoft Entra ID.
 
 From here, you have a few options:
 

docs/integrations/azure-ad/sso-saml.mdx

@@ -1,32 +1,32 @@
 ---
-description: Use Microsoft Azure AD to secure access to ngrok tunnels
+description: Use Microsoft Entra ID to secure access to ngrok tunnels
 ---
 
-# Azure Active Directory SSO (SAML)
+# Microsoft Entra ID SSO (SAML)
 
 :::tip TL;DR
-To have ngrok enforce Single Sign-On using SAML with Azure Active Directory (Azure AD):
+To have ngrok enforce Single Sign-On using SAML with Microsoft Entra ID:
 
 1. [Create an ngrok Edge](#create-edge)
-1. [Create an Azure AD application](#create-app)
+1. [Create a Microsoft Entra ID application](#create-app)
 1. [Update the ngrok Edge with the IdP metadata](#update-ngrok-edge)
 1. [Test your integration](#test-integration)
 1. [Bonus: configure ngrok to enforce authorization based on Azure groups](#bonus)
 
 :::
 
-This article details how to configure Azure AD as an Identity Provider for your ngrok Edge. By integrating Azure AD with ngrok, you can:
+This article details how to configure Microsoft Entra ID as an Identity Provider for your ngrok Edge. By integrating Microsoft Entra ID with ngrok, you can:
 
-- Restrict access to ngrok tunnels to only users who authenticated via Azure AD
-- Configure Azure AD and ngrok to enforce user and group authorization
-- Use Azure AD's dashboard to facilitate access to ngrok applications
+- Restrict access to ngrok tunnels to only users who authenticated via Microsoft Entra ID
+- Configure Microsoft Entra ID and ngrok to enforce user and group authorization
+- Use Microsoft Entra ID's dashboard to facilitate access to ngrok applications
 
 ## Requirements
 
-To configure ngrok tunnels with Azure AD, you must have:
+To configure ngrok tunnels with Microsoft Entra ID, you must have:
 
 - an [ngrok Enterprise Account](https://ngrok.com/pricing) with an authtoken or admin access to configure edges with SAML
-- a Microsoft Azure account with access to an Azure AD tenant
+- a Microsoft Azure account with access to an Microsoft Entra ID tenant
 
 ## Step 1: Create an ngrok Edge {#create-edge}
 
@@ -36,7 +36,7 @@ To configure ngrok tunnels with Azure AD, you must have:
 
     1. Click **New Edge**
     1. Click **HTTPS Edge**
-    1. Click the **Pencil Icon** next to "no description". Enter _Edge With Azure Active Directory SSO_ as the Edge name and click **Save**
+    1. Click the **Pencil Icon** next to "no description". Enter _Edge With Microsoft Entra ID SSO_ as the Edge name and click **Save**
 
 1.  Configure the SAML module for this Edge:
 
@@ -52,11 +52,11 @@ To configure ngrok tunnels with Azure AD, you must have:
 
     1. Click **Save**
 
-    1. Note that ngrok has now generated values for the fields in the Service Provider section. You will need to configure Azure AD with these values later
+    1. Note that ngrok has now generated values for the fields in the Service Provider section. You will need to configure Microsoft Entra ID with these values later
 
-## Step 2: Create an Azure AD application {#create-app}
+## Step 2: Create an Microsoft Entra ID application {#create-app}
 
-1. Go to your [Azure AD tenant in Azure](https://portal.azure.com/#view/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/~/Overview)
+1. Go to your [Microsoft Entra ID tenant in Azure](https://portal.azure.com/#view/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/~/Overview)
 
 1. Create an enterprise application
 
@@ -85,7 +85,7 @@ To configure ngrok tunnels with Azure AD, you must have:
 
 ## Step 3: Update the ngrok Edge with the IdP metadata {#update-ngrok-edge}
 
-1. Back in the ngrok dashboard for your Edge's SAML configuration, upload the XML file generated by Azure AD
+1. Back in the ngrok dashboard for your Edge's SAML configuration, upload the XML file generated by Microsoft Entra ID
 
    ![img/3-1.png](img/3-1.png)
 
@@ -140,7 +140,7 @@ For this step, we assume you have an app running locally (i.e. on localhost:3000
    ![img/5-3.png](img/5-3.png)
 
 1. Click **Save**
-1. Go to your group page and copy the object Id (Azure AD returns group object Ids in the group claim)
+1. Go to your group page and copy the object Id (Microsoft Entra ID returns group object Ids in the group claim)
 
    ![img/5-5.png](img/5-5.png)
 

docs/integrations/azure-logs-ingestion/event-destination.mdx

@@ -128,11 +128,11 @@ You now have a **Data Collection Rule** properly configured for ngrok events, al
 
 These steps were adapted from the [Create a Microsoft Entra Application](https://learn.microsoft.com/en-us/azure/azure-monitor/logs/tutorial-logs-ingestion-portal?source=recommendations#create-microsoft-entra-application) docs from Microsoft.
 
-1. Navigate to the search bar and type in **Entra ID**.
+1. Navigate to the search bar and type in **Microsoft Entra ID**.
 
 2. Select the **Microsoft Entra ID** under **Services**, not the Marketplace item.
 
-![search entra id](img/search-entra.png)
+![search Microsoft Entra ID](img/search-entra.png)
 
 3. Navigate to **Manage -> App registrations** on the sidebar.
 
@@ -146,7 +146,7 @@ These steps were adapted from the [Create a Microsoft Entra Application](https:/
 
 ![register app](img/register.png)
 
-You have now created an **Entra ID App Registration**, which is a service user construct that grants roles/access to services like ngrok.
+You have now created an **Microsoft Entra ID App Registration**, which is a service user construct that grants roles/access to services like ngrok.
 
 ## **Step 5**: Assign IAM permissions to the Application for the DCR {#dcr-iam}
 
@@ -197,7 +197,7 @@ In order to create an event destination in your ngrok Dashboard, we will need to
 - the DCR stream name
 - the DCE log ingestion URI
 
-1. To gather the first three fields, we will navigate back to **Entra ID**. Search for **Entra** in the top search bar and select the **Entra ID** service.
+1. To gather the first three fields, we will navigate back to **Microsoft Entra ID**. Search for **Entra** in the top search bar and select the **Microsoft Entra ID** service.
 
 2. Navigate to **Manage -> App registrations** in the sidebar, and select the application you created in [**Step 4**](#entra-application).