Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into justin-docs

Author: b-ahibbard

articles/app-service/configure-authentication-customize-sign-in-out.md

@@ -65,7 +65,7 @@ The token format varies slightly according to the provider. See the following ta
 > [!NOTE]
 > The GitHub provider for App Service authentication does not support customized sign-in and sign-out.
 
-If the provider token is validated successfully, the API returns with an `authenticationToken` in the response body, which is your session token. 
+If the provider token is validated successfully, the API returns with an `authenticationToken` in the response body, which is your session token. To get more information on the user claims, see [Work with user identities in Azure App Service authentication](configure-authentication-user-identities.md).
 
 ```json
 {

articles/app-service/overview-hosting-plans.md

@@ -32,6 +32,8 @@ The _pricing tier_ of an App Service plan determines what App Service features y
 
 Each tier also provides a specific subset of App Service features. These features include custom domains and TLS/SSL certificates, autoscaling, deployment slots, backups, Traffic Manager integration, and more. The higher the tier, the more features that are available. To find out which features are supported in each pricing tier, see [App Service plan details](https://azure.microsoft.com/pricing/details/app-service/windows/#pricing).
 
+You can find more comparisons between plans at [App Service limits](../azure-resource-manager/management/azure-subscription-service-limits.md#app-service-limits).
+
 <a name="new-pricing-tier-premiumv3"></a>
 
 ## PremiumV3 pricing tier

articles/azure-resource-manager/management/resources-without-resource-group-limit.md

@@ -215,6 +215,10 @@ Some resources have a limit on the number instances per region. This limit is di
 * servers/jobAgents
 * virtualClusters
 
+## Microsoft.SqlVirtualMachine
+
+* sqlVirtualMachines
+
 ## Microsoft.Storage
 
 * storageAccounts

articles/communication-services/concepts/voice-video-calling/calling-sdk-features.md

@@ -7,7 +7,7 @@ manager: chpalm
 services: azure-communication-services
 
 ms.author: micahvivion
-ms.date: 07/25/2024
+ms.date: 10/31/2024
 ms.topic: conceptual
 ms.service: azure-communication-services
 ms.subservice: calling
@@ -128,7 +128,6 @@ The following table represents the set of supported browsers, which are currentl
 - Firefox support is in public preview.
 - Currently, the calling SDK only supports Android System WebView on Android, iOS WebView(WKWebView) in public preview. Other types of embedded browsers or WebView on other OS platforms aren't officially supported, for example, GeckoView, Chromium Embedded Framework (CEF), Microsoft Edge WebView2. Running JavaScript Calling SDK on these platforms isn't actively tested, it might or might not work.
 - [An iOS app on Safari can't enumerate/select mic and speaker devices](../known-issues.md#enumerating-devices-isnt-possible-in-safari-when-the-application-runs-on-ios-or-ipados) (for example, Bluetooth). This issue is a limitation of iOS, and the operating system controls default device selection.
-- iOS Edge browser support is available in public preview in WebJS SDK version [1.30.1-beta.1](https://github.com/Azure/Communication/blob/master/releasenotes/acs-javascript-calling-library-release-notes.md#1301-beta1-2024-10-01) and higher.
 
 ## Calling client - browser security model
 

articles/confidential-computing/confidential-vm-faq.yml

@@ -73,7 +73,7 @@ sections:
           On confidential VMs with a temp disk, the pagefile.sys file can be moved to the encrypted OS [Tips for moving pagefile.sys to the c:\ drive](/azure/virtual-machines/windows/change-drive-letter).
 
       - question: | 
-          Can I generate a memory dump from within my confidential VM?
+          Can I generate a host memory dump from within my confidential VM?
         answer: | 
           No, this capability doesn't exist for confidential VMs.
                   

articles/firewall/index.yml

@@ -29,8 +29,6 @@ landingContent:
         links:
           - text: Azure Firewall rule processing logic
             url: rule-processing.md
-          - text: Frequently asked questions
-            url: firewall-faq.yml
       - linkListType: concept
         links:
           - text: Azure Firewall NAT behaviors
@@ -43,14 +41,7 @@ landingContent:
         links:
           - text: What's new
             url: https://azure.microsoft.com/updates/?category=networking&query=Firewall
-      - linkListType: deploy
-        links: 
-          - text: Provision and configure Azure Firewall and Application Gateway
-            url: https://mslabs.cloudguides.com/en-us/guides/Azure%20Networking%20Solutions%20-%20Exercise%204
-          - text: Secure your network infrastructure with Azure Firewall and Azure DDoS Protection
-            url: https://mslearn.cloudguides.com/guides/Secure%20your%20network%20infrastructure%20with%20Azure%20Firewall%20and%20Azure%20DDoS%20Protection
-          - text: Enhance network visibility and threat detection through Azure network security integrations with Microsoft Sentinel
-            url: https://mslearn.cloudguides.com/guides/Enhance%20network%20visibility%20and%20threat%20detection%20through%20Azure%20network%20security%20integrations%20with%20Microsoft%20Sentinel
+
 
   # Card
   - title: Learn about Azure Firewall Premium
@@ -84,6 +75,24 @@ landingContent:
         links:
           - text: Deploy Firewall Basic
             url: deploy-firewall-basic-portal-policy.md
+      - linkListType: deploy
+        links: 
+          - text: Provision and configure Azure Firewall and Application Gateway
+            url: https://mslabs.cloudguides.com/en-us/guides/Azure%20Networking%20Solutions%20-%20Exercise%204
+          - text: Secure your network infrastructure with Azure Firewall and Azure DDoS Protection
+            url: https://mslearn.cloudguides.com/guides/Secure%20your%20network%20infrastructure%20with%20Azure%20Firewall%20and%20Azure%20DDoS%20Protection
+          - text: Enhance network visibility and threat detection through Azure network security integrations with Microsoft Sentinel
+            url: https://mslearn.cloudguides.com/guides/Enhance%20network%20visibility%20and%20threat%20detection%20through%20Azure%20network%20security%20integrations%20with%20Microsoft%20Sentinel
+
+  # Card
+  - title: Troubleshoot Azure Firewall
+    linkLists:
+      - linkListType: reference
+        links:
+          - text: Azure Firewall known issues and limitations
+            url: firewall-known-issues.md
+          - text: Frequently asked questions
+            url: firewall-faq.yml
 
   # Card
   - title: Learn about Azure Firewall integration in Copilot for Security

articles/operator-nexus/list-of-metrics-collected.md

@@ -314,9 +314,10 @@ Baremetal server metrics are collected and delivered to Azure Monitor per minute
 |NodeNetworkTransmitPackets|Network|Node Network Transmited Packets|Count|Total number of packets transmitted by the node network interfaces. In the absence of data, this metric will retain the most recent value emitted|Device, Host|
 |NodeNetworkStatus|Network|Node Network Up|Count|Indicates the operational status of the nodes network interfaces. Value is 1 if operational state is 'up', 0 otherwise. In the absence of data, this metric will default to 0|Device, Host|
 |NodeNtpLeap|System|Node NTP Leap|Count|The raw leap flag value of the local NTP daemon. This indicates the status of leap seconds. Value is 0 if no adjustment is needed, 1 to add a leap second, 2 to delete a leap second, and 3 if the clock is unsynchronized. In the absence of data, this metric will retain the most recent value emitted|Host|
-|NodeNtpStratum|System|Node NTP Stratum|Count|The stratum level of the local NTP daemon. This indicates the distance from the reference clock, with lower numbers representing closer proximity and higher accuracy. Values range from 1 (directly connected to reference clock) to 15 (further away), with 16 indicating the clock is unsynchronized. In the absence of data, this metric will retain the most recent value emitted|Host|
+|NodeNtpRootDelaySeconds|System|Node NTP Root Delay Seconds|Seconds|Indicates the delay to synchronize with the root server. In the absence of data, this metric will retain the most recent value emitted|Host|
+|NodeNtpRtt (Deprecated)|System|Node NTP RTT|Seconds|Deprecated - Round-trip time from node exporter collector to local NTP daemon. In the absence of data, this metric will retain the most recent value emitted|Host|
 |NodeNtpSanity|System|Node NTP Sanity|Count|The aggregate health of the local NTP daemon. This includes checks for stratum, leap flag, freshness, root distance, and causality violations. Value is 1 if all checks pass, 0 otherwise. In the absence of data, this metric will retain the most recent value emitted|Host|
-|NodeNtpRtt|System|Node NTP RTT|Seconds|Round-trip time from node exporter collector to local NTP daemon. In the absence of data, this metric will retain the most recent value emitted|Host|
+|NodeNtpStratum|System|Node NTP Stratum|Count|The stratum level of the local NTP daemon. This indicates the distance from the reference clock, with lower numbers representing closer proximity and higher accuracy. Values range from 1 (directly connected to reference clock) to 15 (further away), with 16 indicating the clock is unsynchronized. In the absence of data, this metric will retain the most recent value emitted|Host|
 |NodeNvmeInfo|Disk|Node NVMe Info (Preview)|Count|Non-Volatile Memory express (NVMe) information, value is always 1. Provides state for a device. In the absence of data, this metric will default to 0|Device, State|
 |NodeOsInfo|System|Node OS Info|Count|Node OS information, value is always 1. Provides name and version for a device. In the absence of data, this metric will retain the most recent value emitted|Host, Name, Version|
 |NodeProcessState|System|Node Processes State|Count|The number of processes in each state. The possible states are D (UNINTERRUPTABLE_SLEEP), R (RUNNING & RUNNABLE), S (INTERRUPTABLE_SLEEP), T (STOPPED) and Z (ZOMBIE). In the absence of data, this metric will default to 0|Host, State|

articles/operator-nexus/troubleshoot-isolation-domain.md

@@ -4,7 +4,7 @@ description: Troubleshoot isolation domain failures, and learn how to debug fail
 ms.service: azure-operator-nexus
 ms.custom: troubleshooting
 ms.topic: troubleshooting
-ms.date: 05/24/2023
+ms.date: 10/31/2024
 ms.author: v-saambe
 author: v-saambe
 ---

articles/peering-service/location-partners.md

@@ -1,11 +1,11 @@
 ---
 title: Azure Peering Service locations and partners
-description: Learn about the available locations and partners globally for the Azure Peering Service.
+description: Learn about globally available Microsoft Azure Peering Service locations and partners (ISPs and IXPs).
 author: halkazwini
 ms.author: halkazwini
 ms.service: azure-peering-service
 ms.topic: concept-article
-ms.date: 10/28/2024
+ms.date: 10/31/2024
 ms.custom: references_regions
 ---
 
@@ -48,8 +48,9 @@ The following table provides information on the Peering Service connectivity par
 | [Sejong Telecom](https://www.sejongtelecom.net/) | Asia |
 | [Singtel](https://www.singtel.com/business/campaign/singnet-cloud-connect-microsoft-direct) | Asia |
 | [Sunrise](https://www.sunrise.ch/business/en/home). | Europe |
-| [Swisscom](https://www.swisscom.ch/en/business/enterprise/offer/wireline/ip-plus.html) | Europe |
+| [Swisscom](https://www.swisscom.ch/en/business/enterprise/offer/wireline/ip-plus/) | Europe |
 | [Telstra International](https://www.telstra.com.sg/en/products/global-networks/global-internet/global-internet-direct) | Asia, Europe |
+| [TOKAI-NETWORK](https://www.broadline.ne.jp/en/) | Japan  |
 | [Vocusgroup NZ](https://www.vocus.co.nz/microsoftazuredirectpeering/) | Oceania |
 | [Vodacom](https://www.vodacom.com/index.php) | Africa |
 | [Vodafone](https://www.vodafone.com/business/solutions/fixed-connectivity/internet-services#solutions) | Asia, Europe, North America |
@@ -69,7 +70,7 @@ The following table provides information on the Peering Service connectivity par
 | Cape Town | [CMC Networks](https://www.cmcnetworks.net/products/microsoft-azure-peering-services.html), [Liquid Telecom](https://liquidc2.com/connect/#maps) |
 | Dublin | [Vodafone](https://www.vodafone.com/business/solutions/fixed-connectivity/internet-services#solutions) |
 | Frankfurt | [Vodafone](https://www.vodafone.com/business/solutions/fixed-connectivity/internet-services#solutions), [Colt](https://www.colt.net/product/cloud-prioritisation/) |
-| Geneva | [Intercloud](https://www.intercloud.com/partners/microsoft-azure), [Swisscom](https://www.swisscom.ch/en/business/enterprise/offer/wireline/ip-plus.html), [Sunrise](https://www.sunrise.ch/business/en/home) |
+| Geneva | [Intercloud](https://www.intercloud.com/partners/microsoft-azure), [Swisscom](https://www.swisscom.ch/en/business/enterprise/offer/wireline/ip-plus/), [Sunrise](https://www.sunrise.ch/business/en/home) |
 | Hong Kong SAR | [Colt](https://www.colt.net/product/cloud-prioritisation/), [Singtel](https://www.singtel.com/business/campaign/singnet-cloud-connect-microsoft-direct), [Vodafone](https://www.vodafone.com/business/solutions/fixed-connectivity/internet-services#solutions) |
 | Jakarta | [NTT Communications](https://www.ntt.com/en/services/network/software-defined-network.html) |
 | Johannesburg | [CMC Networks](https://www.cmcnetworks.net/products/microsoft-azure-peering-services.html), [Liquid Telecom](https://liquidc2.com/connect/#maps) |
@@ -81,17 +82,17 @@ The following table provides information on the Peering Service connectivity par
 | Manila | [Converge ICT](https://www.convergeict.com/enterprise/microsoft-azure-peering-service-maps/) |
 | Marseilles | [Vodafone](https://www.vodafone.com/business/solutions/fixed-connectivity/internet-services#solutions) |
 | Nairobi | [Liquid Telecom](https://liquidc2.com/connect/#maps) |
-| Osaka | [Colt](https://www.colt.net/product/cloud-prioritisation/), [IIJ](https://www.iij.ad.jp/en/), [NTT Communications](https://www.ntt.com/en/services/network/software-defined-network.html) |
+| Osaka | [Colt](https://www.colt.net/product/cloud-prioritisation/), [IIJ](https://www.iij.ad.jp/en/), [NTT Communications](https://www.ntt.com/en/services/network/software-defined-network.html), [TOKAI-NETWORK](https://www.broadline.ne.jp/en/) |
 | Paris | [Vodafone](https://www.vodafone.com/business/solutions/fixed-connectivity/internet-services#solutions) |
 | Prague | [Vodafone](https://www.vodafone.com/business/solutions/fixed-connectivity/internet-services#solutions) |
 | Singapore | [Singtel](https://www.singtel.com/business/campaign/singnet-cloud-connect-microsoft-direct), [Colt](https://www.colt.net/product/cloud-prioritisation/), [Vodafone](https://www.vodafone.com/business/solutions/fixed-connectivity/internet-services#solutions) |
 | Seoul | [Sejong Telecom](https://www.sejongtelecom.net/) |
 | Sofia | [Vodafone](https://www.vodafone.com/business/solutions/fixed-connectivity/internet-services#solutions) |
 | Sydney | [Kordia](https://www.kordia.co.nz/cloudconnect), [Vocusgroup NZ](https://www.vocus.co.nz/microsoftazuredirectpeering/) |
-| Tokyo | [IIJ](https://www.iij.ad.jp/en/), [Colt](https://www.colt.net/product/cloud-prioritisation/), [NTT Communications](https://www.ntt.com/en/services/network/software-defined-network.html) |
+| Tokyo | [Colt](https://www.colt.net/product/cloud-prioritisation/), [IIJ](https://www.iij.ad.jp/en/), [NTT Communications](https://www.ntt.com/en/services/network/software-defined-network.html), [TOKAI-NETWORK](https://www.broadline.ne.jp/en/) |
 | Vienna | [Vodafone](https://www.vodafone.com/business/solutions/fixed-connectivity/internet-services#solutions) |
 | Warsaw | [Atman](https://www.atman.pl/en/atman-internet-maps/) |
-| Zurich | [Intercloud](https://www.intercloud.com/partners/microsoft-azure), [Swisscom](https://www.swisscom.ch/en/business/enterprise/offer/wireline/ip-plus.html), [Sunrise](https://www.sunrise.ch/business/en/home) |
+| Zurich | [Intercloud](https://www.intercloud.com/partners/microsoft-azure), [Swisscom](https://www.swisscom.ch/en/business/enterprise/offer/wireline/ip-plus/), [Sunrise](https://www.sunrise.ch/business/en/home) |
 
 # [**IXPs by Metro**](#tab/ixp)
 

articles/reliability/reliability-bastion.md

@@ -25,8 +25,7 @@ Azure Bastion is a fully managed PaaS service that you provision to securely con
 
 For production deployments, you should:
 
- - Use standard or premium Azure Bastion resources. While the basic SKU supports zone redundancy, we don't recommend it for production use.
- - [Enable zone redundancy](#availability-zone-support) (in preview), if your Azure Bastion resources are in a supported region.
+ - [Enable zone redundancy](#availability-zone-support), if your Azure Bastion resources are in a supported region.
 
 ## Transient faults
 
@@ -42,28 +41,31 @@ You can specify which availability zone or zones an Azure Bastion resource shoul
 
 :::image type="content" source="media/reliability-bastion/bastion-instances-zones.png" alt-text="Diagram that shows Azure Bastion with three instances, each in a separate availability zone." border="false":::
 
-If you specify more availability zones than you have instances, Azure Bastion spreads instances across as many zones as it can. If an availability zone is unavailable, the instance in the faulty zone will be replaced with another instance in a healthy zone.
 
 > [!NOTE]
-> Azure Bastion support for zone redundancy is currently in preview.
+> If you specify more availability zones than you have instances, Azure Bastion spreads instances across as many zones as it can. If an availability zone is unavailable, the instance in the faulty zone will be replaced with another instance in a healthy zone.
 
 ### Requirements
 
 To configure Azure Bastion resources with zone redundancy you must deploy with the Basic, Standard, or Premium SKUs.
 
 The Developer SKU is intended for non-production use. It doesn't support zone redundancy. However, in the event of a region failure, Azure Bastion attempts to route traffic through different infrastructure.
 
+Bastion requires a Standard SKU zone redundant Public IP.
+
 ### Regions supported
 
 Zone-redundant Azure Bastion resources can be deployed into the following regions:
 
 | Americas | Europe | Middle East | Africa | Asia Pacific |
 |---|---|---|---|---|
 | Canada Central | North Europe | Qatar Central | South Africa North | Australia East |
-| Central US | Sweden Central | | |
+| Central US | Sweden Central | Israel Central | | Korea Central |
 | East US | UK South
 | East US 2 | West Europe | | |
-| West US 2  | | | |
+| West US 2  | Norway East | | |
+| East US 2 EUAP | Italy North | | |
+| Mexico Central| Spain Central | | |
 
 ### Cost