Adjustments to remove final bad link

Author: matternst7258

articles/operator-nexus/howto-service-principal.md

@@ -13,7 +13,7 @@ ms.author: matthewernst
 
 Service principals in Azure are identity entities that are used by applications, services, and automation tools to access specific Azure resources. They can be thought of as 'users' for applications, allowing these applications to interact with Azure services. Service principals provide and control permissions to Azure resources within your subscription, allowing you to specify exactly what actions an application can perform in your environment. 
 
-For more information on how to create a Service principal, reference this [tutorial](/cli/azure/azure-cli-sp-tutorial-1.md) or this [documentation](/entra/architecture/service-accounts-principal).
+For more information on how to create a Service principal, an existing Azure Learn [documentation](/entra/architecture/service-accounts-principal) goes into Service Principal fundamentals.
 
 ## Service principals in Operator Nexus
 
@@ -29,12 +29,12 @@ For information on how to rotate a service principal, reference [how to rotate s
 
 ## Best practices 
 
-The below guidance is a high-level list of recommended security considerations to take into account when managing a new service principal.
+The list is a high-level list of recommended security considerations to take into account when managing a new service principal.
 
 - **Least Privilege**: Assign the minimum permissions necessary for the service principal to perform its function. Avoid assigning broad permissions if they aren't needed.
-- **Lifecycle Management**: Regularly review and update service principals. Remove or disable them when they're no longer needed.
+- **Lifecycle Management**: Regularly review and update service principals. Remove or disable them when not required.
 - **Use Managed Identities**: Where possible, use Azure Managed Identities instead of creating and managing service principals manually.
-- **Secure Secrets**: If a service principal uses a password (client secret), ensure it's stored securely. Consider using Azure Key Vault.
+- **Secure Secrets**: If a service principal uses a password (client secret), ensure credentials are stored securely. Consider using Azure Key Vault.
 - **Monitor Activity**: Use Azure Monitor and Azure Log Analytics to track the activities of your service principals.
 - **Rotation of Secrets**: Regularly rotate and change the service principal's secrets. The maximum recommended duration is 180 days. 
 - **Use Azure Policy**: Implement Azure policies to audit and enforce best practices for service principals.