Merge branch 'main' into specification

Author: v-albemi

.gitignore

@@ -46,3 +46,115 @@ articles/planetary-computer/image_syntax_checker.py
 articles/planetary-computer/image-file-fixer.py
 articles/planetary-computer/orphaned-media.py
 articles/planetary-computer/orphaned_media_files.txt
+articles/planetary-computer/naip-airports.md
+articles/planetary-computer/sentinel-2-l2a-grindavik.md
+articles/planetary-computer/temp_editor.md
+articles/planetary-computer/umbra-sar.md
+articles/planetary-computer/geocatalog_configs/buildingfootprint/mosaics.json
+articles/planetary-computer/geocatalog_configs/buildingfootprint/render-options.json
+articles/planetary-computer/geocatalog_configs/buildingfootprint/stac.json
+articles/planetary-computer/geocatalog_configs/buildingfootprint/tile-settings.json
+articles/planetary-computer/geocatalog_configs/ecmwf-forecast/mosaics.json
+articles/planetary-computer/geocatalog_configs/ecmwf-forecast/render-options.json
+articles/planetary-computer/geocatalog_configs/ecmwf-forecast/stac.json
+articles/planetary-computer/geocatalog_configs/ecmwf-forecast/tile-settings.json
+articles/planetary-computer/geocatalog_configs/esa-cci-lc/mosaics.json
+articles/planetary-computer/geocatalog_configs/esa-cci-lc/render-options.json
+articles/planetary-computer/geocatalog_configs/esa-cci-lc/stac.json
+articles/planetary-computer/geocatalog_configs/esa-cci-lc/tile-settings.json
+articles/planetary-computer/geocatalog_configs/esa-cci-lc-netcdf/mosaics.json
+articles/planetary-computer/geocatalog_configs/esa-cci-lc-netcdf/render-options.json
+articles/planetary-computer/geocatalog_configs/esa-cci-lc-netcdf/stac.json
+articles/planetary-computer/geocatalog_configs/esa-cci-lc-netcdf/tile-settings.json
+articles/planetary-computer/geocatalog_configs/fws-nwi/mosaics.json
+articles/planetary-computer/geocatalog_configs/fws-nwi/stac.json
+articles/planetary-computer/geocatalog_configs/fws-nwi/tile-settings.json
+articles/planetary-computer/geocatalog_configs/fws-nwi-tutorial-943/mosaics.json
+articles/planetary-computer/geocatalog_configs/fws-nwi-tutorial-943/stac.json
+articles/planetary-computer/geocatalog_configs/fws-nwi-tutorial-943/tile-settings.json
+articles/planetary-computer/geocatalog_configs/fws-nwi-tutorial-97/mosaics.json
+articles/planetary-computer/geocatalog_configs/fws-nwi-tutorial-97/stac.json
+articles/planetary-computer/geocatalog_configs/fws-nwi-tutorial-97/tile-settings.json
+articles/planetary-computer/geocatalog_configs/GEBCO_bathymetry/mosaics.json
+articles/planetary-computer/geocatalog_configs/GEBCO_bathymetry/render-options.json
+articles/planetary-computer/geocatalog_configs/GEBCO_bathymetry/stac.json
+articles/planetary-computer/geocatalog_configs/GEBCO_bathymetry/tile-settings.json
+articles/planetary-computer/geocatalog_configs/goes-glm/mosaics.json
+articles/planetary-computer/geocatalog_configs/goes-glm/stac.json
+articles/planetary-computer/geocatalog_configs/goes-glm/tile-settings.json
+articles/planetary-computer/geocatalog_configs/guam-dem/mosaics.json
+articles/planetary-computer/geocatalog_configs/guam-dem/render-options.json
+articles/planetary-computer/geocatalog_configs/guam-dem/stac.json
+articles/planetary-computer/geocatalog_configs/guam-dem/tile-settings.json
+articles/planetary-computer/geocatalog_configs/LA-Fires/mosaics.json
+articles/planetary-computer/geocatalog_configs/LA-Fires/render-options.json
+articles/planetary-computer/geocatalog_configs/LA-Fires/stac.json
+articles/planetary-computer/geocatalog_configs/LA-Fires/tile-settings.json
+articles/planetary-computer/geocatalog_configs/meta-population/render-options.json
+articles/planetary-computer/geocatalog_configs/meta-population/stac.json
+articles/planetary-computer/geocatalog_configs/meta-population/tile-settings.json
+articles/planetary-computer/geocatalog_configs/modis-14A1-061/mosaics.json
+articles/planetary-computer/geocatalog_configs/modis-14A1-061/stac.json
+articles/planetary-computer/geocatalog_configs/modis-14A1-061/tile-settings.json
+articles/planetary-computer/geocatalog_configs/modis-21A2-061/mosaics.json
+articles/planetary-computer/geocatalog_configs/modis-21A2-061/stac.json
+articles/planetary-computer/geocatalog_configs/modis-21A2-061/tile-settings.json
+articles/planetary-computer/geocatalog_configs/monrovia-drone/mosaics.json
+articles/planetary-computer/geocatalog_configs/monrovia-drone/render-options.json
+articles/planetary-computer/geocatalog_configs/monrovia-drone/stac.json
+articles/planetary-computer/geocatalog_configs/monrovia-drone/tile-settings.json
+articles/planetary-computer/geocatalog_configs/naip-airports/mosaics.json
+articles/planetary-computer/geocatalog_configs/naip-airports/render-options.json
+articles/planetary-computer/geocatalog_configs/naip-airports/stac.json
+articles/planetary-computer/geocatalog_configs/naip-airports/tile-settings.json
+articles/planetary-computer/geocatalog_configs/NAIP_Duplin_NC/mosaics.json
+articles/planetary-computer/geocatalog_configs/NAIP_Duplin_NC/render-options.json
+articles/planetary-computer/geocatalog_configs/NAIP_Duplin_NC/stac.json
+articles/planetary-computer/geocatalog_configs/NAIP_Duplin_NC/tile-settings.json
+articles/planetary-computer/geocatalog_configs/nasa-nex-gddp-cmip6/mosaics.json
+articles/planetary-computer/geocatalog_configs/nasa-nex-gddp-cmip6/render-options.json
+articles/planetary-computer/geocatalog_configs/nasa-nex-gddp-cmip6/stac.json
+articles/planetary-computer/geocatalog_configs/nasa-nex-gddp-cmip6/tile-settings.json
+articles/planetary-computer/geocatalog_configs/ndvi_diff/mosaics.json
+articles/planetary-computer/geocatalog_configs/ndvi_diff/render-options.json
+articles/planetary-computer/geocatalog_configs/ndvi_diff/stac.json
+articles/planetary-computer/geocatalog_configs/ndvi_diff/tile-settings.json
+articles/planetary-computer/geocatalog_configs/noaa-climate-normals-netcdf/mosaics.json
+articles/planetary-computer/geocatalog_configs/noaa-climate-normals-netcdf/render-options.json
+articles/planetary-computer/geocatalog_configs/noaa-climate-normals-netcdf/stac.json
+articles/planetary-computer/geocatalog_configs/noaa-climate-normals-netcdf/tile-settings.json
+articles/planetary-computer/geocatalog_configs/noaa-hrrr-sfc-conus/mosaics.json
+articles/planetary-computer/geocatalog_configs/noaa-hrrr-sfc-conus/stac.json
+articles/planetary-computer/geocatalog_configs/noaa-hrrr-sfc-conus/tile-settings.json
+articles/planetary-computer/geocatalog_configs/noaa-hrrr-sfc-conus-test/mosaics.json
+articles/planetary-computer/geocatalog_configs/noaa-hrrr-sfc-conus-test/stac.json
+articles/planetary-computer/geocatalog_configs/noaa-hrrr-sfc-conus-test/tile-settings.json
+articles/planetary-computer/geocatalog_configs/noaa-mrms-qpe-1h-pass1/render-options.json
+articles/planetary-computer/geocatalog_configs/noaa-mrms-qpe-1h-pass1/stac.json
+articles/planetary-computer/geocatalog_configs/noaa-mrms-qpe-1h-pass1/tile-settings.json
+articles/planetary-computer/geocatalog_configs/potsdam-aerial/mosaics.json
+articles/planetary-computer/geocatalog_configs/potsdam-aerial/render-options.json
+articles/planetary-computer/geocatalog_configs/potsdam-aerial/stac.json
+articles/planetary-computer/geocatalog_configs/potsdam-aerial/tile-settings.json
+articles/planetary-computer/geocatalog_configs/sentinel-2-l2a-tutorial-231/mosaics.json
+articles/planetary-computer/geocatalog_configs/sentinel-2-l2a-tutorial-231/render-options.json
+articles/planetary-computer/geocatalog_configs/sentinel-2-l2a-tutorial-231/stac.json
+articles/planetary-computer/geocatalog_configs/sentinel-2-l2a-tutorial-231/tile-settings.json
+articles/planetary-computer/geocatalog_configs/sentinel-2-l2a_Grindavik/mosaics.json
+articles/planetary-computer/geocatalog_configs/sentinel-2-l2a_Grindavik/render-options.json
+articles/planetary-computer/geocatalog_configs/sentinel-2-l2a_Grindavik/stac.json
+articles/planetary-computer/geocatalog_configs/sentinel-2-l2a_Grindavik/tile-settings.json
+articles/planetary-computer/geocatalog_configs/umbra-sar/mosaics.json
+articles/planetary-computer/geocatalog_configs/umbra-sar/render-options.json
+articles/planetary-computer/geocatalog_configs/umbra-sar/stac.json
+articles/planetary-computer/geocatalog_configs/umbra-sar/tile-settings.json
+articles/planetary-computer/geocatalog_configs/umbra-sar-airplanes/mosaics.json
+articles/planetary-computer/geocatalog_configs/umbra-sar-airplanes/render-options.json
+articles/planetary-computer/geocatalog_configs/umbra-sar-airplanes/stac.json
+articles/planetary-computer/geocatalog_configs/umbra-sar-airplanes/tile-settings.json
+articles/planetary-computer/geocatalog_configs/umbra-sar-ships/mosaics.json
+articles/planetary-computer/geocatalog_configs/umbra-sar-ships/render-options.json
+articles/planetary-computer/geocatalog_configs/umbra-sar-ships/stac.json
+articles/planetary-computer/geocatalog_configs/umbra-sar-ships/tile-settings.json
+articles/planetary-computer/helper-content/collection-config-scraper.py
+articles/planetary-computer/helper-content/generate_collection_docs.py

.openpublishing.publish.config.json

@@ -620,6 +620,12 @@
             "branch": "main",
             "branch_mapping": {}
         },
+        {
+            "path_to_root": "app-service-agentic-semantic-kernel-ai-foundry-agent",
+            "url": "https://github.com/Azure-Samples/app-service-agentic-semantic-kernel-ai-foundry-agent",
+            "branch": "main",
+            "branch_mapping": {}
+        },
         {
             "path_to_root": "playwright-testing-service",
             "url": "https://github.com/microsoft/playwright-testing-service",

.openpublishing.redirection.json

@@ -1,5 +1,90 @@
 {
   "redirections": [
+    {
+      "source_path": "articles/fxt-edge-filer/add-nodes.md",
+      "redirect_url": "/previous-versions/azure/fxt-edge-filer/add-nodes",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/fxt-edge-filer/add-storage.md",
+      "redirect_url": "/previous-versions/azure/fxt-edge-filer/add-storage",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/fxt-edge-filer/additional-doc.md",
+      "redirect_url": "/previous-versions/azure/fxt-edge-filer/additional-doc",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/fxt-edge-filer/cluster-create.md",
+      "redirect_url": "/previous-versions/azure/fxt-edge-filer/cluster-create",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/fxt-edge-filer/configure-network.md",
+      "redirect_url": "/previous-versions/azure/fxt-edge-filer/configure-network",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/fxt-edge-filer/index.yml",
+      "redirect_url": "/previous-versions/azure/fxt-edge-filer/index",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/fxt-edge-filer/install.md",
+      "redirect_url": "/previous-versions/azure/fxt-edge-filer/install",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/fxt-edge-filer/monitor.md",
+      "redirect_url": "/previous-versions/azure/fxt-edge-filer/monitor",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/fxt-edge-filer/mount-clients.md",
+      "redirect_url": "/previous-versions/azure/fxt-edge-filer/mount-clients",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/fxt-edge-filer/network-power.md",
+      "redirect_url": "/previous-versions/azure/fxt-edge-filer/network-power",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/fxt-edge-filer/node-password.md",
+      "redirect_url": "/previous-versions/azure/fxt-edge-filer/node-password",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/fxt-edge-filer/overview.md",
+      "redirect_url": "/previous-versions/azure/fxt-edge-filer/overview",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/fxt-edge-filer/port-list.md",
+      "redirect_url": "/previous-versions/azure/fxt-edge-filer/port-list",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/fxt-edge-filer/power-off.md",
+      "redirect_url": "/previous-versions/azure/fxt-edge-filer/power-off",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/fxt-edge-filer/specs.md",
+      "redirect_url": "/previous-versions/azure/fxt-edge-filer/specs",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/fxt-edge-filer/support-ticket.md",
+      "redirect_url": "/previous-versions/azure/fxt-edge-filer/support-ticket",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/fxt-edge-filer/supported-ciphers.md",
+      "redirect_url": "/previous-versions/azure/fxt-edge-filer/supported-ciphers",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/backup/azure-elastic-storage-area-network-backup-manage.md",
       "redirect_url": "/azure/backup/azure-elastic-san-backup-manage",

articles/active-directory-b2c/media/partner-nok-nok/nok-nok-id-token-hint-architecture-diagram.png

@@ -7,7 +7,7 @@ manager: martinco
 ms.reviewer: kengaderdus
 ms.service: azure-active-directory
 ms.topic: how-to
-ms.date: 01/26/2024
+ms.date: 06/30/2025
 ms.author: gasinh
 ms.subservice: b2c
 
@@ -21,20 +21,19 @@ In this article, you can learn how to configure the [Cloudflare Web Application
 
 ## Prerequisites
 
-To get started, you'll need:
+To get started, you need:
 
-- An Azure subscription 
-  - If you don't have one, you can get an [Azure free account](https://azure.microsoft.com/free/)
-- [An Azure AD B2C tenant](tutorial-create-tenant.md) linked to your Azure subscription
-- A [Cloudflare](https://dash.cloudflare.com/sign-up) account
+- An Azure subscription. If you don't have one, you can get an [Azure free account](https://azure.microsoft.com/free/).
+- [An Azure AD B2C tenant](tutorial-create-tenant.md) linked to your Azure subscription.
+- A [Cloudflare](https://dash.cloudflare.com/sign-up) account.
 
 ## Scenario description
 
 Cloudflare WAF integration includes the following components:
 
-- **Azure AD B2C tenant** – The authorization server that verifies user credentials using the custom policies defined in the tenant. It's known as the identity provider
+- **Azure AD B2C tenant** – The authorization server that verifies user credentials using the custom policies defined in the tenant, known as the identity provider.
 - [**Azure Front Door**](../frontdoor/front-door-overview.md) – Enables custom domains for Azure B2C tenant. Traffic from Cloudflare WAF is routed to Azure Front Door before arriving at Azure AD B2C tenant.
-- **Cloudflare** – The web application firewall that manages traffic sent to the authorization server
+- **Cloudflare** – The web application firewall that manages traffic sent to the authorization server.
 
 ## Integrate with Azure AD B2C
 
@@ -58,6 +57,9 @@ The settings appear in the following image.
 
    ![Screenshot of proxied status.](./media/partner-cloudflare/select-proxied.png)
 
+> [!NOTE]
+> Azure Front Door-managed certificates aren't automatically renewed if your custom domain’s CNAME record points to a DNS record other than the Azure Front Door endpoint’s domain (for example, when using a third-party DNS service like Cloudflare). To renew the certificate in such cases, follow the instructions in the [Renew Azure Front Door-managed certificates](../frontdoor/domain.md#renew-azure-front-door-managed-certificates) article.
+
 ### Configure the Web Application Firewall
 
 Go to your Cloudflare settings, and use the Cloudflare content to [configure the WAF](https://www.cloudflare.com/application-services/products/waf/) and learn about other security tools. 

articles/active-directory-b2c/partner-cloudflare.md

@@ -40,7 +40,7 @@ To enable passkey authentication for your users, enable Nok Nok as an identity p
 
 The following diagram illustrates the Nok Nok solution as an IdP for Azure AD B2C by using OpenID Connect (OIDC) for passkey authentication.
 
-![Diagram of Nok Nok as IdP for Azure AD B2C using OpenID Connect (OIDC) for passkey authentication.](./media/partner-nok-nok/nok-nok-architecture-diagram.png)
+![Diagram for passkey authentication with Nok Nok as an IdP.](./media/partner-nok-nok/nok-nok-architecture-diagram.png)
 
 ### Scenario 1: Passkey registration
 1. The user navigates to the Nok Nok tutorial web app using the link provided by Nok Nok.
@@ -52,9 +52,11 @@ The following diagram illustrates the Nok Nok solution as an IdP for Azure AD B2
 ### Scenario 2: Passkey authentication
 1. The user selects the sign-in with Nok Nok Cloud button on the Azure AD B2C sign-in page.
 2. Azure AD B2C redirects the user to the Nok Nok sign-in app.
-3. The user authenticates with their passkey.
-4. The Nok Nok server validates the passkey assertion and sends an OIDC authentication response to Azure AD B2C.
-5. Based on the authentication result, Azure AD B2C either grants or denies access to the target application.
+3. The user requests passkey authentication
+4. The user authenticates with their passkey.
+5. The Nok Nok Cloud validates the passkey assertion
+6. The Nok Nok Cloud sends an OIDC authentication response to Azure AD B2C.
+7. Based on the authentication result, Azure AD B2C either grants or denies access to the target application.
 
 ## Get started with Nok Nok
 
@@ -125,6 +127,22 @@ For the following instructions, Nok Nok is a new OIDC IdP in the B2C identity pr
 
 If the flow is incomplete, confirm the user is or isn't saved in the directory.
 
+## Alternate flow for Authentication
+
+The following diagram illustrates an alternate passkey sign in or sign up flow using the ID Token Hint feature of Azure AD B2C. With this approach, an Azure custom policy verifies the ID Token Hint produced by the Nok Nok Cloud. For more details, please refer to the article, [Define an ID token hint technical profile in an Azure Active Directory B2C custom policy](./id-token-hint.md). Please contact Nok Nok support for help with integrated the required Azure custom policy.
+
+![Diagram for passkey authentication using ID Token Hint from Nok Nok.](./media/partner-nok-nok/nok-nok-id-token-hint-architecture-diagram.png)
+
+The following are the steps
+1. The user selects the sign-in with Nok Nok Cloud button.
+2. The Nok Nok Cloud request passkey authentication.
+3. The user authenticates with their passkey.
+4. The Nok Nok Cloud validates the passkey assertion.
+5. The ID Token Hint is returned.
+6. The App posts an OIDC request with the ID Token Hint to Azure AD B2C.
+7. Azure AD B2C Custom Policy verifies the ID Token Hint.
+8. Based on the authentication result, Azure AD B2C either grants or denies access to the target application.
+
 ## Next steps
 
 * [Azure AD B2C custom policy overview](./custom-policy-overview.md)