Merge pull request #253808 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: v-alje

articles/active-directory/authentication/howto-sspr-windows.md

@@ -193,6 +193,7 @@ HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\Credential Provide
 
 - To enable verbose logging, create a `REG_DWORD: "EnableLogging"`, and set it to 1.
 - To disable verbose logging, change the `REG_DWORD: "EnableLogging"` to 0.
+- Review the debug logging in the Application event log under source AADPasswordResetCredentialProvider.
 
 ## What do users see
 

articles/active-directory/develop/apple-sso-plugin.md

@@ -61,7 +61,7 @@ Use the following information to enable the SSO plug-in by using MDM.
 
 If you use Microsoft Intune as your MDM service, you can use built-in configuration profile settings to enable the Microsoft Enterprise SSO plug-in:
 
-1. Configure the [SSO app extension](/mem/intune/configuration/device-features-configure#single-sign-on-app-extension) settings of a configuration profile. 
+1. Configure the [SSO app plug-in](/mem/intune/configuration/use-enterprise-sso-plug-in-ios-ipados-with-intune) settings of a configuration profile. 
 1. If the profile isn't already assigned, [assign the profile to a user or device group](/mem/intune/configuration/device-profile-assign).
 
 The profile settings that enable the SSO plug-in are automatically applied to the group's devices the next time each device checks in with Intune.

articles/ai-services/speech-service/includes/quickstarts/stt-diarization/cpp.md

@@ -66,12 +66,12 @@ Follow these steps to create a new console application and install the Speech SD
         std::promise<void> recognitionEnd;
 
         // Subscribes to events.
-        conversationTranscriber->Transcribing.Connect([](const SpeechRecognitionEventArgs& e)
+        conversationTranscriber->Transcribing.Connect([](const ConversationTranscriptionEventArgs& e)
             {
                 std::cout << "TRANSCRIBING:" << e.Result->Text << std::endl;
             });
 
-        conversationTranscriber->Transcribed.Connect([](const SpeechRecognitionEventArgs& e)
+        conversationTranscriber->Transcribed.Connect([](const ConversationTranscriptionEventArgs& e)
             {
                 if (e.Result->Reason == ResultReason::RecognizedSpeech)
                 {
@@ -84,7 +84,7 @@ Follow these steps to create a new console application and install the Speech SD
                 }
             });
 
-        conversationTranscriber->Canceled.Connect([&recognitionEnd](const SpeechRecognitionCanceledEventArgs& e)
+        conversationTranscriber->Canceled.Connect([&recognitionEnd](const ConversationTranscriptionCanceledEventArgs& e)
             {
                 auto cancellation = CancellationDetails::FromResult(e.Result);
                 std::cout << "CANCELED: Reason=" << (int)cancellation->Reason << std::endl;

articles/cosmos-db/how-to-develop-emulator.md

@@ -476,7 +476,8 @@ Use the [Azure Cosmos DB API for NoSQL .NET SDK](nosql/quickstart-dotnet.md) to
     >     {
     >         ServerCertificateCustomValidationCallback = HttpClientHandler.DangerousAcceptAnyServerCertificateValidator
     >     }),
-    >     ConnectionMode = ConnectionMode.Gateway
+    >     ConnectionMode = ConnectionMode.Gateway,
+    >     LimitToEndpoint = true
     > };
     >
     > using CosmosClient client = new(

articles/dns/dns-private-resolver-overview.md

@@ -106,7 +106,7 @@ The following restrictions hold with respect to virtual networks:
 ### Subnet restrictions 
 
 Subnets used for DNS resolver have the following limitations:
-- A subnet must be a minimum of /28 address space or a maximum of /24 address space. A /28 subnet is sufficient to accomodate current endpoint limits. A subnet size of /27 to /24 can provide flexibility if these limits change.
+- A subnet must be a minimum of /28 address space or a maximum of /24 address space. A /28 subnet is sufficient to accommodate current endpoint limits. A subnet size of /27 to /24 can provide flexibility if these limits change.
 - A subnet can't be shared between multiple DNS resolver endpoints. A single subnet can only be used by a single DNS resolver endpoint.
 - All IP configurations for a DNS resolver inbound endpoint must reference the same subnet. Spanning multiple subnets in the IP configuration for a single DNS resolver inbound endpoint isn't allowed.
 - The subnet used for a DNS resolver inbound endpoint must be within the virtual network referenced by the parent DNS resolver.

articles/healthcare-apis/includes/healthcare-apis-azure-api-fhir-retirement.md

@@ -8,7 +8,5 @@ ms.author: jasteppe
 ---
 
 > [!IMPORTANT]
-> **Azure API for FHIR will be retired on September 30, 2026.** Follow the [migration strategies](../fhir/migration-strategies.md) to transition to Azure Health Data Services FHIR service by that date. Due to the transition of Azure API for FHIR to Azure Health Data Services, new deployments won't be allowed beginning April 1, 2025. 
-
+> **Azure API for FHIR will be retired on September 30, 2026.** Follow the [migration strategies](../fhir/migration-strategies.md) to transition to **Azure Health Data Services FHIR service** by that date. Due to the retirement of Azure API for FHIR, new deployments won't be allowed beginning April 1, 2025. 
 [Azure Health Data Services FHIR service](../healthcare-apis-overview.md) is the evolved version of Azure API for FHIR that enables customers to manage [FHIR](../fhir/overview.md), DICOM, and MedTech services with integrations into other Azure services.
- 

articles/machine-learning/how-to-deploy-online-endpoints.md

@@ -368,7 +368,7 @@ To configure a deployment:
 ```python
 model = Model(path="../model-1/model/sklearn_regression_model.pkl")
 env = Environment(
-    conda_file="../model-1/environment/conda.yml",
+    conda_file="../model-1/environment/conda.yaml",
     image="mcr.microsoft.com/azureml/openmpi4.1.0-ubuntu20.04:latest",
 )
 

articles/mysql/flexible-server/concepts-audit-logs.md

@@ -66,7 +66,7 @@ The following sections describe the output of MySQL audit logs based on the even
 | `ResourceProvider` | Name of the resource provider. Always `MICROSOFT.DBFORMYSQL` |
 | `ResourceType` | `Servers` |
 | `ResourceId` | Resource URI |
-| `Resource` | Name of the server |
+| `Resource` | Name of the server in upper case |
 | `Category` | `MySqlAuditLogs` |
 | `OperationName` | `LogEvent` |
 | `LogicalServerName_s` | Name of the server |
@@ -97,7 +97,7 @@ Schema below applies to GENERAL, DML_SELECT, DML_NONSELECT, DML, DDL, DCL, and A
 | `ResourceProvider` | Name of the resource provider. Always `MICROSOFT.DBFORMYSQL` |
 | `ResourceType` | `Servers` |
 | `ResourceId` | Resource URI |
-| `Resource` | Name of the server |
+| `Resource` | Name of the server in upper case|
 | `Category` | `MySqlAuditLogs` |
 | `OperationName` | `LogEvent` |
 | `LogicalServerName_s` | Name of the server |
@@ -128,7 +128,7 @@ Schema below applies to GENERAL, DML_SELECT, DML_NONSELECT, DML, DDL, DCL, and A
 | `ResourceProvider` | Name of the resource provider. Always `MICROSOFT.DBFORMYSQL` |
 | `ResourceType` | `Servers` |
 | `ResourceId` | Resource URI |
-| `Resource` | Name of the server |
+| `Resource` | Name of the server in upper case|
 | `Category` | `MySqlAuditLogs` |
 | `OperationName` | `LogEvent` |
 | `LogicalServerName_s` | Name of the server |
@@ -148,7 +148,7 @@ Once your audit logs are piped to Azure Monitor Logs through Diagnostic Logs, yo
 
     ```kusto
     AzureDiagnostics
-    | where Resource  == '<your server name>'
+    | where Resource  == '<your server name>' //Server name must be in Upper case
     | where Category == 'MySqlAuditLogs' and event_class_s == "general_log"
     | project TimeGenerated, Resource, event_class_s, event_subclass_s, event_time_t, user_s , ip_s , sql_text_s
     | order by TimeGenerated asc nulls last
@@ -158,7 +158,7 @@ Once your audit logs are piped to Azure Monitor Logs through Diagnostic Logs, yo
 
     ```kusto
     AzureDiagnostics
-    | where Resource  == '<your server name>'
+    | where Resource  == '<your server name>' //Server name must be in Upper case
     | where Category == 'MySqlAuditLogs' and event_class_s == "connection_log"
     | project TimeGenerated, Resource, event_class_s, event_subclass_s, event_time_t, user_s , ip_s , sql_text_s
     | order by TimeGenerated asc nulls last
@@ -168,7 +168,7 @@ Once your audit logs are piped to Azure Monitor Logs through Diagnostic Logs, yo
 
     ```kusto
     AzureDiagnostics
-    | where Resource  == '<your server name>'
+    | where Resource  == '<your server name>' //Server name must be in Upper case
     | where Category == 'MySqlAuditLogs'
     | project TimeGenerated, Resource, event_class_s, event_subclass_s, event_time_t, user_s , ip_s , sql_text_s
     | summarize count() by event_class_s, event_subclass_s, user_s, ip_s
@@ -178,7 +178,7 @@ Once your audit logs are piped to Azure Monitor Logs through Diagnostic Logs, yo
 
     ```kusto
     AzureDiagnostics
-    | where Resource  == '<your server name>'
+    | where Resource  == '<your server name>' //Server name must be in Upper case
     | where Category == 'MySqlAuditLogs'
     | project TimeGenerated, Resource, event_class_s, event_subclass_s, event_time_t, user_s , ip_s , sql_text_s
     | summarize count() by Resource, bin(TimeGenerated, 5m)

articles/static-web-apps/apis-container-apps.md

@@ -35,7 +35,7 @@ To link a container app to your static web app, you need to have an existing Con
 
 ## Example
 
-Consider an existing Azure App Service instance that exposes an endpoint via the following location.
+Consider an existing Azure Container App instance that exposes an endpoint via the following location.
 
 ```url
 https://my-container-app.red-river-123.eastus2.azurecontainerapps.io/api/getProducts

articles/virtual-machines/b-series-cpu-credit-model/b-series-cpu-credit-model.md

@@ -41,8 +41,8 @@ Similarly, utilizing the example of a Standard_B32as_v2 VM size, if the workload
 
 
 ## Credit monitoring
-To monitor B-series specific credit metrics, customers can utilize the Azure monitor data platform, see [Overview of metrics in Microsoft Azure](../../azure-monitor/data-platform.md). Azure monitor data platform can be accessed via Azure portal and other orchestration paths, and via programmatic API calls to Azure monitor.
-Via Azure monitor data platform, customers can access B-series credit model specific metrics such as 'CPU Credits Consumed', 'CPU Credits Remaining' and 'Percentage CPU' for their given B-series size in real time.  
+To monitor B-series specific credit metrics, customers can utilize the Azure monitor data platform, see [Overview of metrics in Microsoft Azure](../../azure-monitor/data-platform.md). Azure monitor data platform can be accessed via the Azure portal and other orchestration paths, and via programmatic API calls to Azure monitor.
+Via Azure monitor data platform, customers can access B-series credit model-specific metrics such as 'CPU Credits Consumed', 'CPU Credits Remaining', and 'Percentage CPU' for their given B-series size in real time.  
 
 
 ## Other sizes and information