fix url issues; does not add /manuaal/ yet

Author: akristen

content/manuals/admin/company/_index.md

@@ -25,13 +25,13 @@ grid:
   - title: Configure single sign-on
     description: Discover how to configure SSO for your entire company.
     icon: key
-    link: /security/for-admins/single-sign-on/
+    link: /enterprise/security/single-sign-on/
   - title: Set up SCIM
     description:
       Set up SCIM to automatically provision and deprovision users in your
       company.
     icon: checklist
-    link: /security/for-admins/provisioning/scim/
+    link: /enterprise/security/provisioning/scim/
   - title: Domain management
     description: Add and verify your company's domains.
     icon: domain_verification

content/manuals/admin/company/users.md

@@ -33,7 +33,7 @@ to invite members to.
    > [!NOTE]
    >
    > When you invite members, you assign them a role.
-   > See [Roles and permissions](/security/for-admins/roles-and-permissions/)
+   > See [Roles and permissions](/enterprise/security/roles-and-permissions/core-roles/)
    > for details about the access permissions for each role.
 
    Pending invitations appear on the Members page. The invitees receive an

content/manuals/enterprise/security/provisioning/scim/provision-scim.md

@@ -35,7 +35,7 @@ For additional details about supported attributes and SCIM, see
 > your SCIM values.
 >
 > Alternatively, you can disable JIT provisioning to rely solely on SCIM.
-> For details, see [Just-in-Time](just-in-time.md).
+> For details, see [Just-in-Time](/enterprise/security/provisioning/just-in-time).
 
 ## Enable SCIM in Docker
 
@@ -219,7 +219,7 @@ group will inherit these attributes upon provisioning.
 
 ### Step one: Configure attribute mappings
 
-1. Complete the [SCIM provisioning setup](#enable-scim-in-docker).
+1. Complete the [SCIM provisioning setup](/enterprise/security/provisioning/scim/provision-scim/#enable-scim-in-docker).
 1. In the Azure Portal, open **Microsoft Entra ID** >
    **Enterprise Applications**, and select your SCIM application.
 1. Go to **Provisioning** > **Mappings** >
@@ -228,7 +228,7 @@ group will inherit these attributes upon provisioning.
    - `userPrincipalName` -> `userName`
    - `mail` -> `emails.value`
    - Optional. Map `dockerRole`, `dockerOrg`, or `dockerTeam` using one of the
-     [mapping methods](#step-two-choose-a-role-mapping-method).
+     [mapping methods](/enterprise/security/provisioning/scim/provision-scim/#set-up-role-mapping).
 1. Remove any unsupported attributes to prevent sync errors.
 1. Optional. Go to **Mappings** > **Provision Azure Active Directory Groups**:
    - If group provisioning causes errors, set **Enabled** to **No**.

content/manuals/enterprise/security/single-sign-on/_index.md

@@ -49,11 +49,11 @@ assigned to an organization, and added to a team.
 > [!IMPORTANT]
 >
 > Docker plans to deprecate CLI password-based sign-in in future releases.
-Using a PAT ensures continued CLI access. For more information, see the
-[security announcement](/manuals/security/security-announcements.md#deprecation-of-password-logins-on-cli-when-sso-enforced).
+> Using a PAT ensures continued CLI access. For more information, see the
+> [security announcement](/security/security-announcements.> md#deprecation-of-password-logins-on-cli-when-sso-enforced).
 
 ## Next steps
 
 - Start [configuring SSO](connect.md).
-- Read the [FAQs](/enterprise/security/single-sign-on/faqs/general).
-- [Troubleshoot](/enterprise/security/single-sign-on/faqs/troubleshoot-sso/) SSO issues.
+- Read the [FAQs](/enterprise/security/single-sign-on/FAQs/general).
+- [Troubleshoot](/enterprise/security/single-sign-on/troubleshoot-sso) SSO issues.