diff --git a/.github/workflows/azure-prod-build-deploy.yml b/.github/workflows/azure-prod-build-deploy.yml
index 06da6426068b..06ac18399adf 100644
--- a/.github/workflows/azure-prod-build-deploy.yml
+++ b/.github/workflows/azure-prod-build-deploy.yml
@@ -61,12 +61,11 @@ jobs:
# Create a temporary token for the Azure Container Registry
# and set it as a GitHub Actions environment variable
- # Then clean up by deleting the temp token.
# Created token are viewable in the ACR resource UI
# under Repository permissions > Tokens
- name: 'Create Azure Container Registry Token'
env:
- PROD_REGISTRY_SERVER: ${{ secrets.PROD_REGISTRY_SERVER }}
+ CONTAINER_REGISTRY_SERVER: ${{ secrets.PROD_REGISTRY_SERVER }}
run: npm run create-acr-token
- name: 'Docker login'
diff --git a/.github/workflows/validate-github-github-docs-urls.yml b/.github/workflows/validate-github-github-docs-urls.yml
index e93d9f803660..c1df3d211661 100644
--- a/.github/workflows/validate-github-github-docs-urls.yml
+++ b/.github/workflows/validate-github-github-docs-urls.yml
@@ -8,15 +8,16 @@ on:
workflow_dispatch:
schedule:
- cron: '20 16 * * 1' # Run every Monday at 16:20 UTC / 8:20 PST
- pull_request:
- paths:
- - 'content/**'
- # In case a relevant dependency changes
- - 'package*.json'
- # The scripts
- - 'src/links/scripts/validate-github-github-docs-urls/**'
- # The workflow
- - .github/workflows/validate-github-github-docs-urls.yml
+ # See https://gh.io/AAsyyao before uncommenting:
+ # pull_request:
+ # paths:
+ # - 'content/**'
+ # # In case a relevant dependency changes
+ # - 'package*.json'
+ # # The scripts
+ # - 'src/links/scripts/validate-github-github-docs-urls/**'
+ # # The workflow
+ # - .github/workflows/validate-github-github-docs-urls.yml
permissions:
contents: read
diff --git a/content/actions/hosting-your-own-runners/managing-self-hosted-runners/managing-access-to-self-hosted-runners-using-groups.md b/content/actions/hosting-your-own-runners/managing-self-hosted-runners/managing-access-to-self-hosted-runners-using-groups.md
index fe8e90b0735c..54cbe2387e4d 100644
--- a/content/actions/hosting-your-own-runners/managing-self-hosted-runners/managing-access-to-self-hosted-runners-using-groups.md
+++ b/content/actions/hosting-your-own-runners/managing-self-hosted-runners/managing-access-to-self-hosted-runners-using-groups.md
@@ -2,7 +2,7 @@
title: Managing access to self-hosted runners using groups
shortTitle: Manage access with runner groups
intro: You can use policies to limit access to self-hosted runners that have been added to an organization{% ifversion ghec or ghes %} or enterprise{% endif %}.
-permissions: 'Enterprise accounts, organizations owned by enterprise accounts, and organizations using {% data variables.product.prodname_team %} can create and manage additional runner groups.
{% ifversion custom-org-roles %}Users with the "Manage organization runners and runner groups" permission can manage runner groups at the organization level.{% endif %}'
+permissions: 'Enterprise accounts, organizations owned by enterprise accounts, and organizations using {% data variables.product.prodname_team %} or {% data variables.product.prodname_free_user %} plans can create and manage additional runner groups using self-hosted runners.
{% ifversion custom-org-roles %}Users with the "Manage organization runners and runner groups" permission can manage runner groups at the organization level.{% endif %}'
redirect_from:
- /actions/hosting-your-own-runners/managing-self-hosted-runners/managing-access-to-self-hosted-runners
- /actions/hosting-your-own-runners/managing-access-to-self-hosted-runners
diff --git a/content/admin/copilot-business-only/setting-up-a-dedicated-enterprise-for-copilot-business-managed-users.md b/content/admin/copilot-business-only/setting-up-a-dedicated-enterprise-for-copilot-business-managed-users.md
index 8f6401edffbc..a2d3138734ef 100644
--- a/content/admin/copilot-business-only/setting-up-a-dedicated-enterprise-for-copilot-business-managed-users.md
+++ b/content/admin/copilot-business-only/setting-up-a-dedicated-enterprise-for-copilot-business-managed-users.md
@@ -20,7 +20,7 @@ This article describes the setup for an **enterprise with managed users**. If yo
## Prerequisites
-* To provision users, you must connect the enterprise account to an identity management system. {% data variables.product.company_short %} partners with some developers of identity management systems to provide a "paved-path" integration with {% data variables.product.prodname_emus %}. See "[AUTOTITLE](/admin/identity-and-access-management/understanding-iam-for-enterprises/about-enterprise-managed-users#identity-management-systems)."
+* To provision users, you must connect the enterprise account to an identity management system. {% data variables.product.company_short %} partners with some developers of identity management systems to provide a "paved-path" integration with {% data variables.product.prodname_emus %}. Alternatively, you can use any system, or combination of systems, that conforms to SAML 2.0 and SCIM 2.0. However, support for resolving problems with these systems may be limited. See "[AUTOTITLE](/admin/identity-and-access-management/understanding-iam-for-enterprises/about-enterprise-managed-users#identity-management-systems)."
{% data reusables.copilot-business-for-non-ghe.prerequisites %}
## Requesting an enterprise account
diff --git a/content/admin/managing-iam/understanding-iam-for-enterprises/getting-started-with-enterprise-managed-users.md b/content/admin/managing-iam/understanding-iam-for-enterprises/getting-started-with-enterprise-managed-users.md
index 0ec499e51091..52bf95738513 100644
--- a/content/admin/managing-iam/understanding-iam-for-enterprises/getting-started-with-enterprise-managed-users.md
+++ b/content/admin/managing-iam/understanding-iam-for-enterprises/getting-started-with-enterprise-managed-users.md
@@ -60,6 +60,8 @@ To get started, read the guide for your chosen authentication method.
* "[AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)"
* "[AUTOTITLE](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)"
+{% data variables.product.company_short %} offers a "paved-path" integration and full support if you use a partner IdP for both authentication and provisioning. Alternatively, you can use any system, or combination of systems, that conforms to SAML 2.0 and SCIM 2.0. However, support for resolving problems with these systems may be limited. For more details, see "[AUTOTITLE](/admin/identity-and-access-management/understanding-iam-for-enterprises/about-enterprise-managed-users#identity-management-systems)."
+
## Configure provisioning
After you configure authentication, you can configure SCIM provisioning, which is how your IdP will create {% data variables.enterprise.prodname_managed_users %} on {% data variables.product.prodname_dotcom %}. See "[AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users)."
diff --git a/content/billing/using-the-new-billing-platform/estimating-spending-for-your-enterprise.md b/content/billing/using-the-new-billing-platform/estimating-spending-for-your-enterprise.md
index d5ad3c558e2d..2867652463b2 100644
--- a/content/billing/using-the-new-billing-platform/estimating-spending-for-your-enterprise.md
+++ b/content/billing/using-the-new-billing-platform/estimating-spending-for-your-enterprise.md
@@ -24,7 +24,7 @@ The "Overview" page provides a high-level view of your spending and budgets.
On this page, you can view your usage in the following categories:
* **Current metered usage:** The card on the top left shows the gross metered usage for your enterprise including all cost centers. Click **More details** to view a breakdown of the usage by cost center.
-* **Metered usage (w/o cost centers):** The graph shows the gross metered usage for your enterprise excluding cost centers. To view the usage for a specific cost center, select {% octicon "triangle-down" aria-label="Change cost center selection" %}, then click a cost center.
+* **Metered usage:** The graph shows the gross metered usage for your enterprise including cost centers.
To view a different time period, select **Time Frame**, then choose a time period. You can also download an image of the graph by clicking {% octicon "kebab-horizontal" aria-label="Open column options" %} on the right.
diff --git a/content/billing/using-the-new-billing-platform/gathering-insights-on-your-spending.md b/content/billing/using-the-new-billing-platform/gathering-insights-on-your-spending.md
index 2f8c1e1b3c98..2537c9afe477 100644
--- a/content/billing/using-the-new-billing-platform/gathering-insights-on-your-spending.md
+++ b/content/billing/using-the-new-billing-platform/gathering-insights-on-your-spending.md
@@ -24,8 +24,7 @@ You can view the usage of your enterprise members and download the usage data fo
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.billing.enterprise-billing-menu %}
1. Click **Usage**.
-1. To view usage for a specific cost center, click **Metered usage (w/o cost centers) {% octicon "triangle-down" aria-label="Change cost center selection" %}**, then select a cost center.
-1. To search or filter the graph, click the search bar. When you click the search bar, you will see a list of suggested filters.
+1. To search or filter the graph, click the search bar. Then click the filter you want to use.
1. To further filter the graph, use the dropdown menus.
* To see the usage by group, select **Group**, then click a group.
diff --git a/data/reusables/actions/azure-vnet-supported-regions.md b/data/reusables/actions/azure-vnet-supported-regions.md
index 021a96bf7742..ceb813d45fc1 100644
--- a/data/reusables/actions/azure-vnet-supported-regions.md
+++ b/data/reusables/actions/azure-vnet-supported-regions.md
@@ -17,6 +17,7 @@ The {% data variables.product.prodname_actions %} service supports a subset of a
SwitzerlandNorth
UkSouth
SoutheastAsia
+KoreaCentral
Azure private networking supports GPU runners in the following regions.
diff --git a/src/audit-logs/lib/config.json b/src/audit-logs/lib/config.json
index 6d77e73b4193..53f5a7a61024 100644
--- a/src/audit-logs/lib/config.json
+++ b/src/audit-logs/lib/config.json
@@ -3,5 +3,5 @@
"apiOnlyEvents": "This event is not available in the web interface, only via the REST API, audit log streaming, or JSON/CSV exports.",
"apiRequestEvent": "This event is only available via audit log streaming."
},
- "sha": "cdccf7613c6f26c2c5542d8481cf8dacb617a94b"
+ "sha": "d5e464291d8f2559b1c5b7398c16d43c61f79548"
}
\ No newline at end of file
diff --git a/src/workflows/acr-create-token.ts b/src/workflows/acr-create-token.ts
index ba18ebac7fdc..4a17817ca211 100755
--- a/src/workflows/acr-create-token.ts
+++ b/src/workflows/acr-create-token.ts
@@ -9,7 +9,7 @@ type IsoDateString = string
dotenv.config()
const acrTokenName = process.env.ACR_TOKEN_NAME
-const acrProdRegistryServer = process.env.PROD_REGISTRY_SERVER
+const acrServer = process.env.CONTAINER_REGISTRY_SERVER
const repo = process.env.GITHUB_REPOSITORY
function main() {
@@ -23,7 +23,7 @@ function main() {
try {
const cmd = `az acr token create \
--name ${acrTokenName} \
- --registry ${acrProdRegistryServer} \
+ --registry ${acrServer} \
--repository ${repo} \
content/write \
content/read \