paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 38 Packages Projects Releases Wiki Activity

Updated Azure Active Directory to Entra ID

Browse Source 
Microsoft have renamed Azure Active Directory to Entra ID.  https://learn.microsoft.com/en-us/azure/active-directory/fundamentals/new-name .  This PR updates references to AAD to refer to Entra ID.

* On each documentation page, I include `formerly Azure Active Directory` in the first non heading reference to Entra ID.  This will help anyone unfaimiliar withthe  name change, and will also mean the page continues to show up in search results if people search for the old name.
* I didn't correct references in file names, as this would cause broken links.  If we have a way of redirecting those to new urls I can look at doign that, but if not, I think it's better to leave existing links working.
* There were a few references to AAD in release notes for older versions - I left these alone as the product naming was correct at the time of the release notes.
* LDAP provider still has references to "Active Directory" as these reference to the on premise Active Directory, not Azure Active Directory

Signed-off-by: Alex Crome <afscrome@users.noreply.github.com>
This commit is contained in:
Alex Crome
2023-10-19 21:24:47 +01:00
parent bae9015f2b
commit 243c655a68
12 changed files with 37 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/features/kubernetes/authentication.md
+2 -2
View File
@@ -11,7 +11,7 @@ add custom providers there if needed.
These providers are configured so your Kubernetes plugin can locate and access the
clusters you have access to, some of them have special requirements in the third party in
question, like Azure's Managed AAD subscription or Azure RBAC support active on the cluster.
question, like Microsoft Entra ID (formerly Azure Active Directory) subscription or Azure RBAC support active on the cluster.
The providers currently available are divided into server side and client side.
@@ -78,7 +78,7 @@ You get both, the cluster `url` and `caData` directly from the AWS console by go
### Azure
The Azure server side authentication provider works by authenticating on the server with
the Azure CLI, please note that [Azure AD Authentication][1] is a requirement and has to
the Azure CLI, please note that [Microsoft Entra authentication][1] is a requirement and has to
be enabled in your AKS cluster, then follow these steps:
- [Install the Azure CLI][2] in the environment where the backstage application will run.