diff --git a/src/content/docs/reference-architecture/diagrams/sase/augment-access-with-serverless.mdx b/src/content/docs/reference-architecture/diagrams/sase/augment-access-with-serverless.mdx
index 701a2cc78814e23..974bc155a0054df 100644
--- a/src/content/docs/reference-architecture/diagrams/sase/augment-access-with-serverless.mdx
+++ b/src/content/docs/reference-architecture/diagrams/sase/augment-access-with-serverless.mdx
@@ -52,7 +52,7 @@ The following outlines how organizations can run their own custom business logic
 
 ### 1. Custom authorization process using your own rules
 
-During policy evaluation, the [external evaluation](https://developers.cloudflare.com/cloudflare-one/policies/access/external-evaluation/) rule allows for executing your own code during access policy evaluation. In this example an API exposed by Cloudflare Workers receives data about the user making the request, the important part being their username. 
+During policy evaluation, the [external evaluation](/cloudflare-one/policies/access/external-evaluation/) rule allows for executing your own code during access policy evaluation. In this example an API exposed by Cloudflare Workers receives data about the user making the request, the important part being their username.
 
 The code typically makes  calls to either a [database](https://developers.cloudflare.com/d1/) or another API to evaluate if the passed username has access to the application. The external evaluation rule requires that the call returns either a True or False, and this is combined with the policy to determine access.