Merge pull request #220871 from TomJanetscheck/patch-3

Update plan-defender-for-servers-roles.md

Author: prmerger-automator[bot]

articles/defender-for-cloud/plan-defender-for-servers-roles.md

@@ -21,12 +21,12 @@ This article is the third in the Defender for Servers planning guide series. Bef
 
 ## Determine access and ownership
 
-In complex enterprises, different teams manage different [security functions](/cloud-adoption-framework/organize/cloud-security).
+In complex enterprises, different teams manage different [security functions](/azure/cloud-adoption-framework/organize/cloud-security).
 
 Figuring out ownership for server and endpoint security is critical. Ownership that's undefined, or hidden within organizational silos, causes friction that leads to delays, insecure deployments, and difficulties for security operations (SecOps) teams who need to identify and follow threats across the enterprise.
 
 - Security leadership should identify the teams, roles, and individuals responsible for making and implementing decisions about server security.
-- Typically, responsibility is shared between a [central IT team](/cloud-adoption-framework/organize/central-it) and a [cloud infrastructure and endpoint security team](/cloud-adoption-framework/organize/cloud-security-infrastructure-endpoint).
+- Typically, responsibility is shared between a [central IT team](/azure/cloud-adoption-framework/organize/central-it) and a [cloud infrastructure and endpoint security team](/azure/cloud-adoption-framework/organize/cloud-security-infrastructure-endpoint).
 
 Individuals in these teams need Azure access rights to manage and use Defender for Cloud. As part of planning, figure out the right level of access for individuals, based on Defender for Cloud's role-base access control (RBAC) model.