fix links

src/pentesting-cloud/azure-security/README.md

@@ -132,7 +132,7 @@ Get-AzRoleAssignment -SignInName test@corp.onmicrosoft.com # For current user
 
 ### ENtra ID Enumeration
 
-By default, any user should have **enough permissions to enumerate** things such us, users, groups, roles, service principals... (check [default AzureAD permissions](az-basic-information/#default-user-permissions)).\
+By default, any user should have **enough permissions to enumerate** things such us, users, groups, roles, service principals... (check [default AzureAD permissions](az-basic-information/index.html#default-user-permissions)).\
 You can find here a guide:
 
 {{#ref}}

src/pentesting-cloud/azure-security/az-lateral-movement-cloud-on-prem/README.md

@@ -51,7 +51,7 @@ From the **compromised machine to the cloud**:
 
 From compromising **AD** to compromising the **Cloud** and from compromising the **Cloud to** compromising **AD**:
 
-- [**Azure AD Connect**](azure-ad-connect-hybrid-identity/)
+- [**Azure AD Connect**](azure-ad-connect-hybrid-identity/index.html)
 - **Another way to pivot from could to On-Prem is** [**abusing Intune**](../az-services/intune.md)
 
 #### [Roadtx](https://github.com/dirkjanm/ROADtools)

src/pentesting-cloud/azure-security/az-privilege-escalation/az-virtual-machines-and-network-privesc.md

@@ -171,7 +171,7 @@ Set-AzVMDscExtension `
 
 <summary>Hybrid Runbook Worker</summary>
 
-This is a VM extension that would allow to execute runbooks in VMs from an automation account. For more information check the [Automation Accounts service](../az-services/az-automation-account/).
+This is a VM extension that would allow to execute runbooks in VMs from an automation account. For more information check the [Automation Accounts service](../az-services/az-automation-account/index.html).
 
 </details>
 

src/pentesting-cloud/azure-security/az-services/az-azuread.md

@@ -1015,7 +1015,7 @@ It allows the admin to configure it to **block** attempts when the risk is "Low
 
 ### Entra Password Protection
 
-Entra Password Protection ([https://portal.azure.com/#view/Microsoft_AAD_ConditionalAccess/PasswordProtectionBlade](https://portal.azure.com/#view/Microsoft_AAD_ConditionalAccess/PasswordProtectionBlade)) is a security feature that **helps prevent the abuse of weak passwords in by locking out accounts when several unsuccessful login attempts happen**.\
+Entra Password Protection ([https://portal.azure.com/index.html#view/Microsoft_AAD_ConditionalAccess/PasswordProtectionBlade](https://portal.azure.com/#view/Microsoft_AAD_ConditionalAccess/PasswordProtectionBlade)) is a security feature that **helps prevent the abuse of weak passwords in by locking out accounts when several unsuccessful login attempts happen**.\
 It also allows to **ban a custom password list** that you need to provide.
 
 It can be **applied both** at the cloud level and on-premises Active Directory.

src/pentesting-cloud/azure-security/az-services/az-function-apps.md

@@ -56,12 +56,12 @@ In a **Windows** function using NodeJS the code was located in **`C:\home\site\w
 
 ### **Managed Identities & Metadata**
 
-Just like [**VMs**](vms/), Functions can have **Managed Identities** of 2 types: System assigned and User assigned.
+Just like [**VMs**](vms/index.html), Functions can have **Managed Identities** of 2 types: System assigned and User assigned.
 
 The **system assigned** one will be a managed identity that **only the function** that has it assigned would be able to use, while the **user assigned** managed identities are managed identities that **any other Azure service will be able to use**.
 
 > [!NOTE]
-> Just like in [**VMs**](vms/), Functions can have **1 system assigned** managed identity and **several user assigned** ones, so it's always important to try to find all of them if you compromise the function because you might be able to escalate privileges to several managed identities from just one Function.
+> Just like in [**VMs**](vms/index.html), Functions can have **1 system assigned** managed identity and **several user assigned** ones, so it's always important to try to find all of them if you compromise the function because you might be able to escalate privileges to several managed identities from just one Function.
 >
 > If a no system managed identity is used but one or more user managed identities are attached to a function, by default you won’t be able to get any token.
 

src/pentesting-cloud/azure-security/az-services/vms/README.md

@@ -635,7 +635,7 @@ Set-AzVMDscExtension `
 
 <summary>Hybrid Runbook Worker</summary>
 
-This is a VM extension that would allow to execute runbooks in VMs from an automation account. For more information check the [Automation Accounts service](../az-automation-account/).
+This is a VM extension that would allow to execute runbooks in VMs from an automation account. For more information check the [Automation Accounts service](../az-automation-account/index.html).
 
 </details>