Merge pull request #295557 from kenwith/patch-8

Updates to relative link to resolve build issue.

Author: prmerger-automator[bot]

articles/app-service/includes/deploy-intelligent-apps/deploy-intelligent-apps-linux-python-pivot.md

@@ -89,7 +89,7 @@ For Azure OpenAI, see [this documentation](/azure/ai-services/openai/quickstart?
 - Model name: The name of the chat completion model, like "gpt-4o".
 - Deployment name: This is sometimes the same as the model name, but you may have chosen to use a different name. This differentiates between different deployments of the same model.
 - Endpoint: A URL like "https://cog-xxk4qzq3tahic.openai.azure.com/"
-- API version: The desired API version, like "2024-10-21". See the [version history documentation](https://learn.microsoft.com/azure/ai-services/openai/api-version-deprecation) for the latest version.
+- API version: The desired API version, like "2024-10-21". See the [version history documentation](/azure/ai-services/openai/api-version-deprecation) for the latest version.
 
 For OpenAI, see this [documentation](https://platform.openai.com/docs/api-reference) to retrieve the API keys. For our application, you need the following values:
 

articles/azure-resource-manager/troubleshooting/error-storage-account-name.md

@@ -133,10 +133,10 @@ name: '${storageNamePrefix}${uniqueString(resourceGroup().id)}'
 ## Cause 2
 
 The storage account was recently deleted.
-   - If a request to create the storage account comes from a different subscription and tenant than where it was previously located, it will be denied for security purposes as described here, [Prevent dangling DNS entries and avoid subdomain takeover](https://docs.microsoft.com/azure/security/fundamentals/subdomain-takeover). 
+   - If a request to create the storage account comes from a different subscription and tenant than where it was previously located, it will be denied for security purposes as described here, [Prevent dangling DNS entries and avoid subdomain takeover](/azure/security/fundamentals/subdomain-takeover). 
 
 ## Solution 2
 
-[Create a Support Request](https://learn.microsoft.com/azure/azure-portal/supportability/how-to-create-azure-support-request#create-a-support-request****) and choose **Create new storage account** for the problem type, and **Failure(s) during new account creation** for the Problem subtype. Please make sure to include the name of the storage account and the approximate time when account creation failed.
+[Create a Support Request](/azure/azure-portal/supportability/how-to-create-azure-support-request#create-a-support-request****) and choose **Create new storage account** for the problem type, and **Failure(s) during new account creation** for the Problem subtype. Please make sure to include the name of the storage account and the approximate time when account creation failed.
 
 ---