Update broken external links (weekly report #23722) (#62600)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Anne-Marie <102995847+am-stead@users.noreply.github.com>

Author: 3 people

content/actions/tutorials/build-and-test-code/nodejs.md

@@ -31,7 +31,7 @@ This guide shows you how to create a continuous integration (CI) workflow that b
 We recommend that you have a basic understanding of Node.js, YAML, workflow configuration options, and how to create a workflow file. For more information, see:
 
 * [AUTOTITLE](/actions/how-tos/write-workflows)
-* [Getting started with Node.js](https://nodejs.org/en/docs/guides/getting-started-guide/)
+* [Getting started with Node.js](https://nodejs.org/learn/getting-started/introduction-to-nodejs)
 
 {% data reusables.actions.enterprise-setup-prereq %}
 

content/admin/managing-iam/provisioning-user-accounts-with-scim/configuring-authentication-and-provisioning-with-pingfederate.md

@@ -48,7 +48,7 @@ In addition:
 * You may need to configure the firewall in PingFederate to allow outbound connections to {% ifversion ghes %}the `https://HOSTNAME/api/v3/scim/v2` endpoint on your {% data variables.product.prodname_ghe_server %} instance.{% else %}the SCIM endpoints on {% data variables.product.github %}:
   * For **{% data variables.product.prodname_dotcom_the_website %}**: `https://api.github.com/scim/v2/enterprises/ENTERPRISE`
   * For **{% data variables.enterprise.data_residency_site %}**: `https://api.SUBDOMAIN.ghe.com/scim/v2/enterprises/SUBDOMAIN`{% endif %}
-* PingFederate's "provisioner mode" must be set to a value that allows SCIM provisioning. See the "Before you begin" section in PingIdentity's [Configuring outbound provisioning settings](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/help_protocolsettingstasklet_saasglobalprovisioningsettingsstate.html) guide.
+* PingFederate's "provisioner mode" must be set to a value that allows SCIM provisioning. See the "Before you begin" section in PingIdentity's [Configuring outbound provisioning settings](https://docs.pingidentity.com/pingfederate/13.1/administrators_reference_guide/pf_configuring_outbound_provisioning_settings.html) guide.
 * During this procedure, you will need to upload an X509 certificate to PingFederate. You may want to create and store the certificate before proceeding. You will also need the challenge password for the certificate. See the [Example of creating an X509 certificate](#example-of-creating-an-x509-certificate) section later in this article.
 {%- ifversion ghec %}
 * During this procedure, you will need to upload a SAML metadata file to PingFederate. If you're setting up an enterprise that uses **{% data variables.enterprise.data_residency_short %} on {% data variables.enterprise.data_residency_site %}**, it is easiest to create this file before you start. See [Creating a SAML metadata file for {% data variables.enterprise.data_residency_site %}](#creating-a-saml-metadata-file-for-ghecom).

content/admin/managing-iam/provisioning-user-accounts-with-scim/troubleshooting-team-membership-with-identity-provider-groups.md

@@ -88,7 +88,7 @@ If you see an `external_identity.scim_api_incomplete` or `external_group.scim_ap
 Re-trigger provisioning from your identity provider for the affected user or group. SCIM operations are idempotent, so re-provisioning will not create duplicates.
 
 * **Entra ID:** In the Microsoft Entra admin center, go to **Enterprise Applications** > your SCIM app > **Provisioning**, and use **Provision on demand** for the affected user or group, or **Restart provisioning** for a full sync. For more information, see [On-demand provisioning in Microsoft Entra ID](https://learn.microsoft.com/en-us/entra/identity/app-provisioning/provision-on-demand) in the Microsoft documentation.
-* **Okta:** Re-push the affected group from **Push Groups**, or re-assign the app to the affected user. For more information, see [Push Groups](https://help.okta.com/en-us/content/topics/users-groups/usgr-push-groups.htm) in the Okta documentation.
+* **Okta:** Re-push the affected group from **Push Groups**, or re-assign the app to the affected user. For more information, see [Group push](https://help.okta.com/en-us/content/topics/users-groups-profiles/usgp-about-group-push.htm) in the Okta documentation.
 * **Other identity providers:** Consult your identity provider's documentation for how to re-trigger SCIM provisioning for a specific user or group.
 
 ### Checking if the change was applied

content/code-security/concepts/vulnerability-reporting-and-management/github-advisory-database.md

@@ -122,14 +122,14 @@ The Exploit Prediction Scoring System, or EPSS, is a system devised by the globa
 
 The {% data variables.product.prodname_advisory_database %} includes EPSS scores from FIRST for advisories containing CVEs with corresponding EPSS data. {% data variables.product.company_short %} also displays the EPSS score percentile, which is the proportion of all scored vulnerabilities with the same or a lower EPSS score.
 
-For example, if an advisory had an EPSS score that had a percentage of 90.534% at the 95th percentile, according to the [EPSS model](https://www.first.org/epss/model), this means that:
+For example, if an advisory had an EPSS score that had a percentage of 90.534% at the 95th percentile, according to the [EPSS model](https://www.first.org/epss/using-epss), this means that:
 
 * There is a 90.534% chance of this vulnerability being exploited in the wild in the next 30 days.
 * 95% of the total modeled vulnerabilities are considered less likely to be exploited in the next 30 days than this vulnerability.
 
-Extended information about how to interpret this data can be found in FIRST's EPSS User Guide. This information helps you understand how both percentage and percentile can be used to interpret the likelihood that a vulnerability could be exploited in the wild according to FIRST's model. For more information, see the [FIRST's EPSS User Guide](https://www.first.org/epss/user-guide) on the FIRST website.
+Extended information about how to interpret this data can be found in FIRST's EPSS documentation. This information helps you understand how both percentage and percentile can be used to interpret the likelihood that a vulnerability could be exploited in the wild according to FIRST's model. For more information, see [FIRST's EPSS](https://www.first.org/epss/) on the FIRST website.
 
-FIRST also provides additional information around the distribution of their EPSS data. For more information, see [EPSS data and statistics documentation](https://www.first.org/epss/data_stats) on the FIRST website.
+FIRST also provides additional information around the distribution of their EPSS data. For more information, see [EPSS data and statistics documentation](https://www.first.org/epss/data) on the FIRST website.
 
 >[!NOTE] {% data variables.product.company_short %} keeps EPSS data up to date with a daily synchronization action. While EPSS score percentages will always be fully synchronized, score percentiles will only be updated when significantly different.
 

content/copilot/how-tos/chat-with-copilot/chat-in-ide.md

@@ -213,7 +213,7 @@ To leave feedback about the {% data variables.copilot.copilot_chat %} extension,
 ## Further reading
 
 * [AUTOTITLE](/copilot/concepts/prompting/prompt-engineering)
-* [Using {% data variables.copilot.copilot_chat_short %} in {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/copilot/copilot-chat) and [Getting started with {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/copilot/getting-started) in the {% data variables.product.prodname_vscode %} documentation
+* [Using {% data variables.copilot.copilot_chat_short %} in {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/copilot/copilot-chat) in the {% data variables.product.prodname_vscode %} documentation
 * [AUTOTITLE](/copilot/how-tos/copilot-on-github/use-copilot-agents/manage-and-track-agents)
 * [AUTOTITLE](/copilot/how-tos/copilot-on-github/chat-with-copilot/chat-in-github)
 * [AUTOTITLE](/copilot/responsible-use/chat)

content/copilot/tutorials/cloud-agent/improve-a-project.md

@@ -200,4 +200,4 @@ Now that you have created issues, the next step is to delegate an issue to {% da
 
 ## Next steps
 
-Read this case study on the {% data variables.product.github %} blog: [How the {% data variables.product.github %} billing team uses the {% data variables.copilot.copilot_cloud_agent_short %} in {% data variables.product.prodname_copilot %} to continuously burn down technical debt](https://github.blog/ai-and-ml/github-copilot/how-the-github-billing-team-uses-the-cloud-agent-in-github-copilot-to-continuously-burn-down-technical-debt/).
+Read this case study on the {% data variables.product.github %} blog: [How the {% data variables.product.github %} billing team uses the {% data variables.copilot.copilot_cloud_agent_short %} in {% data variables.product.prodname_copilot %} to continuously burn down technical debt](https://github.blog/ai-and-ml/github-copilot/how-the-github-billing-team-uses-the-coding-agent-in-github-copilot-to-continuously-burn-down-technical-debt/).

content/copilot/tutorials/reduce-technical-debt.md

@@ -376,4 +376,4 @@ After reading this tutorial, do you feel confident you can use {% data variables
 * [AUTOTITLE](/copilot/how-tos/use-copilot-agents/cloud-agent)
 * [AUTOTITLE](/copilot/tutorials/refactor-code)
 * [How to use GitHub Copilot in your IDE: Tips, tricks, and best practices](https://github.blog/developer-skills/github/how-to-use-github-copilot-in-your-ide-tips-tricks-and-best-practices/) in the {% data variables.product.company_short %} blog
-* [5 ways to integrate GitHub {% data variables.copilot.copilot_cloud_agent %} into your workflow](https://github.blog/ai-and-ml/github-copilot/5-ways-to-integrate-github-copilot-cloud-agent-into-your-workflow/) in the {% data variables.product.company_short %} blog
+* [5 ways to integrate GitHub {% data variables.copilot.copilot_cloud_agent %} into your workflow](https://github.blog/ai-and-ml/github-copilot/5-ways-to-integrate-github-copilot-coding-agent-into-your-workflow/) in the {% data variables.product.company_short %} blog

src/links/lib/excluded-links.yml

@@ -179,3 +179,9 @@
 
 # registry.modelcontextprotocol.io blocks automated link checkers.
 - startsWith: https://registry.modelcontextprotocol.io/
+
+# marketplace.microsoft.com returns 403 from CI runners (bot-blocking).
+- startsWith: https://marketplace.microsoft.com/
+
+# dotnet.microsoft.com returns 403 from CI runners (bot-blocking).
+- startsWith: https://dotnet.microsoft.com/