Merge branch 'main' into jjgriff93/2511-ui-airlock-filter_requests

docs/tre-admins/auth.md

@@ -67,3 +67,18 @@ App registrations (represented by service principals) define the various access
 Some of the applications require **admin consent** to allow them to validate users against the AAD. Check the Microsoft Docs on [Configure the admin consent workflow](https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/configure-admin-consent-workflow) on how to request admin consent and handle admin consent requests.
 
 We strongly recommend that you use `make auth` to create the AAD assets as this has been tested extensively. Should you wish to create these manually via the [Azure Portal](https://docs.microsoft.com/azure/active-directory/develop/quickstart-register-app); more information can be found [here](./identities/auth-manual.md).
+
+### Enabling users
+
+For a user to gain access to the system, they have to:
+
+1. Have an identity in Azure AD
+1. Be linked with an app registration and assigned a role
+
+When these requirements are met, the user can sign-in using their credentials and use their privileges to use the API, login to workspace environment etc. based on their specific roles.
+
+![User linked with app registrations](../assets/aad-user-linked-with-app-regs.png)
+
+The users can also be linked via the Enterprise application view:
+
+![Adding users to Enterprise application](../assets/adding-users-to-enterprise-application.png)

docs/tre-admins/identities/test-account.md

@@ -88,18 +88,3 @@ On the "Application permissions" section, select "TRE Administrators".
 Back on the main permissions page, click on "Grant admin consent". Once done, you should see "Granted" in the "Status" column, as shown below.
 
 ![Screenshot of Azure portal showing admin consent granted](../../assets/tre-automation-admin-consent-granted.png)
-
-### Enabling users
-
-For a user to gain access to the system, they have to:
-
-1. Have an identity in Azure AD
-1. Be linked with an app registration and assigned a role
-
-When these requirements are met, the user can sign-in using their credentials and use their privileges to use the API, login to workspace environment etc. based on their specific roles.
-
-![User linked with app registrations](../../assets/aad-user-linked-with-app-regs.png)
-
-The users can also be linked via the Enterprise application view:
-
-![Adding users to Enterprise application](../../assets/adding-users-to-enterprise-application.png)

docs/using-tre/index.md

@@ -14,13 +14,13 @@ It contains all the required tooling to develop your custom templates and deploy
 
 ### AzureTRE Reference
 
-AzureTRE deployment repository allows you to reference AzureTRE as a folder, but also uses it in its deployment. See [AzureTRE deployment readme](https://github.com/microsoft/AzureTRE-Deployment/blob/main/README.md) to learn more about it.
+AzureTRE deployment repository allows you to reference AzureTRE as a folder, but also uses it in its deployment. See [AzureTRE Deployment readme](https://github.com/microsoft/AzureTRE-Deployment) to learn more about it.
 
 ## Getting Started
 
 To get started with AzureTRE follow the next steps:
 
-1. Go to [AzureTRE Deployment repository]((https://github.com/microsoft/AzureTRE-Deployment))
+1. Go to [AzureTRE Deployment repository](https://github.com/microsoft/AzureTRE-Deployment)
 1. Click on use this template to set up your project from this template:
 
 [![Use AzureTRE Deployment template](../assets/using-tre/use_template.png)](../assets/using-tre/use_template.png)