Merge pull request #280330 from MicrosoftDocs/main

7/9 11:00 AM IST Publish

Author: PhilKang0704

articles/ai-studio/how-to/deploy-models-serverless.md

@@ -183,7 +183,6 @@ For models offered through the Azure Marketplace, you can deploy them to serverl
                 "type": "Microsoft.MachineLearningServices/workspaces/marketplaceSubscriptions",
                 "apiVersion": "2024-04-01",
                 "name": "[concat(parameters('project_name'), '/', parameters('subscription_name'))]",
-                "location": "[parameters('location')]",
                 "properties": {
                     "modelId": "[parameters('model_id')]"
                 }

articles/aks/howto-deploy-java-quarkus-app.md

@@ -6,7 +6,7 @@ author: dlepow
 
 ms.service: api-management
 ms.topic: concept-article
-ms.date: 06/20/2024
+ms.date: 07/08/2024
 ms.author: danlep
 ms.custom: references_regions
 ---
@@ -53,10 +53,14 @@ The v2 tiers are available in the following regions:
 * France Central
 * Germany West Central
 * North Europe
+* Norway East
 * West Europe
+* Switzerland North
 * UK South
 * UK West
+* South Africa North
 * Central India
+* South India
 * Brazil South
 * Australia Central
 * Australia East

articles/api-management/v2-service-tiers-overview.md

@@ -314,7 +314,7 @@ You can use the `ForEach -Parallel` construct to process commands for each item
    |VMs|Enter the names of the virtual machines using the following syntax: `["VM1","VM2","VM3"]`|
    |Action|Enter `stop` or `start`.|
 
-1. Navigate to your list of virtual machines and refresh the page every few seconds. Observe that the action for each VM happens in parallel. Without the `-Parallel` keyword, the actions would have performed sequentially. While the VMs will start sequentially, each VM may reach the **Running** phase at slightly different times based on the characteristics of each VM.
+1. Navigate to your list of virtual machines and refresh the page every few seconds. Observe that the action for each VM happens in parallel. Without the `-Parallel` keyword, the actions would have performed sequentially. While the VMs will start in parallel, each VM may reach the **Running** phase at slightly different times based on the characteristics of each VM.
 
 ## Clean up resources
 

articles/automation/learn/automation-tutorial-runbook-textual.md

@@ -51,10 +51,12 @@ To allow access from the Automation system managed identity to the Azure SQL dat
     1. Go to [Azure portal](https://portal.azure.com) home page and select **SQL servers**.
     1. In the **SQL server** page, under **Settings**, select **SQL Databases**.
     1. Select your database to go to the SQL database page and select **Query editor (preview)** and execute the following two queries:
-       - CREATE USER "AutomationAccount" FROM EXTERNAL PROVIDER WITH OBJECT_ID= `ObjectID`
-       - EXEC sp_addrolemember `db_owner`, "AutomationAccount"
-           - Automation account - replace with your Automation account's name
-           - Object ID - replace with object (principal) ID for your system managed identity principal from step 1.
+       ```sql
+       # AutomationAccount - replace with your Automation account's name
+       # ObjectID - replace with object (principal) ID for your system managed identity principal from step 1.
+       CREATE USER "AutomationAccount" FROM EXTERNAL PROVIDER WITH OBJECT_ID = `ObjectID`
+       EXEC sp_addrolemember `db_owner`, "AutomationAccount"
+       ```
 
 ## Sample code
 

articles/automation/manage-sql-server-in-automation.md

@@ -34,7 +34,7 @@ To see how all Azure Arc-enabled components are validated, see [Validation progr
 
 |Solution and version | Kubernetes version | Azure Arc-enabled data services version | SQL engine version | PostgreSQL server version|
 |-----|-----|-----|-----|-----|
-|[PowerStore](https://www.dell.com/en-us/shop/powerstore/sf/power-store)|1.25.15|1.25.0_2023-11-14|16.0.5100.7246|Not validated|
+|[PowerStore 4.0](https://www.dell.com/en-us/shop/powerstore/sf/power-store)|1.28.10|1.30.0_2024-06-11|16.0.5349.20214|Not validated|
 |[Unity XT](https://www.dell.com/en-us/dt/storage/unity.htm) |1.24.3|1.15.0_2023-01-10|16.0.816.19223 |Not validated|
 |[PowerFlex](https://www.dell.com/en-us/dt/storage/powerflex.htm) |1.25.0 |1.21.0_2023-07-11 |16.0.5100.7242 |14.5 (Ubuntu 20.04) |
 

articles/azure-arc/data/validation-program.md

@@ -479,7 +479,6 @@ The Azure Maps Routing service (preview) contains different levels of geographic
 | Kazakhstan                             | Good                |                       | ✓                 | ✓                         |
 | Kenya                                  | Good                | ✓                     | ✓                 | ✓                         |
 | Kiribati                               | Major Roads Only    |                       | ✓                 |                            |
-| Korea                                  | Good                | ✓                     |                   |                            |
 | Kosovo                                 | Good                |                       |                   |                            |
 | Kuwait                                 | Good                | ✓                     | ✓                 | ✓                         |
 | Kyrgyzstan                             | Major Roads Only    |                       | ✓                 |                            |

articles/azure-maps/routing-coverage.md

@@ -0,0 +1,66 @@
+---
+title: Guest OS family 2, 3, and 4 retirement notice | Microsoft Docs
+description: Information about when the Azure Guest OS Family 2, 3, and 4 retirement happened and how to determine if you're affected.
+services: cloud-services
+ms.subservice: auto-os-updates
+author: raiye
+manager: timlt
+ms.service: cloud-services
+ms.topic: article
+ms.date: 07/08/2024
+ms.author: raiye
+ms.custom: compute-evergreen
+---
+
+# Guest OS Family 2, 3, and 4 retirement notice
+
+The retirement of Azure Guest OS Families 2, 3, and 4 was announced in July 2024, with the following end-of-life dates: 
+- **Windows Server 2008 R2:** December 2024 
+- **Windows Server 2012 and Windows Server 2012 R2:** February 2025 
+
+If you have questions, visit the [Microsoft question page for Cloud Services](/answers/topics/azure-cloud-services.html) or [contact Azure support](https://azure.microsoft.com/support/options/).
+
+## Are you affected?
+
+Your Cloud Services or [Cloud Services Extended Support](../cloud-services-extended-support/overview.md) are affected if any one of the following applies:
+
+1. You have a value of `osFamily` = `2`, `3`, or `4` explicitly specified in the `ServiceConfiguration.cscfg` file for your Cloud Service.
+1. The Azure portal lists your Guest Operating System family value as *Windows Server 2008 R2*, *Windows Server 2012*, or *Windows Server 2012 R2*. 
+
+To find which of your cloud services are running which OS Family, you can run the following script in Azure PowerShell, though you must [set up Azure PowerShell](/powershell/azure/) first.
+
+```powershell
+foreach($subscription in Get-AzureSubscription) {
+    Select-AzureSubscription -SubscriptionName $subscription.SubscriptionName
+
+    $deployments=get-azureService | get-azureDeployment -ErrorAction Ignore | where {$_.SdkVersion -NE ""}
+
+    $deployments | ft @{Name="SubscriptionName";Expression={$subscription.SubscriptionName}}, ServiceName, SdkVersion, Slot, @{Name="osFamily";Expression={(select-xml -content $_.configuration -xpath "/ns:ServiceConfiguration/@osFamily" -namespace $namespace).node.value }}, osVersion, Status, URL
+}
+```
+
+Your cloud services are impacted by this retirement if the `osFamily` column in the script output contains a `2`, `3`, `4`, or is empty. If empty, the default `osFamily` column value is `5`. 
+
+## Recommendations
+
+If you're affected, we recommend you migrate your Cloud Service or [Cloud Services Extended Support](../cloud-services-extended-support/overview.md) roles to one of the supported Guest OS Families:
+
+**Guest OS family 7.x** - Windows Server 2022 *(recommended)* 
+
+1. Ensure that your application is using Visual Studio 2019 or newer with Azure Development Workload as selected and your application is targeting .NET framework version 4.8 or newer. 
+1. Set the osFamily attribute to "7" in the `ServiceConfiguration.cscfg` file, and redeploy your cloud service. 
+
+**Guest OS family 6.x** - Windows Server 2019 
+
+1. Ensure that your application is using SDK 2.9.6 or later and your application is targeting .NET framework 3.5 or 4.7.2 or newer. 
+1. Set the osFamily attribute to "6" in the `ServiceConfiguration.cscfg` file, and redeploy your cloud service. 
+
+## Important clarification regarding support 
+
+The announcement of the retirement of Azure Guest OS Families 2, 3, and 4, effective May 2025, pertains specifically to the operating systems within these families. This retirement doesn't extend the overall support timeline for Azure Cloud Services (classic) beyond the scheduled deprecation in August 2024. [Cloud Services Extended Support](../cloud-services-extended-support/overview.md) continues support with Guest OS Families 5 and newer. 
+
+Customers currently using Azure Cloud Services who wish to continue receiving support beyond August 2024 are encouraged to transition to [Cloud Services Extended Support](../cloud-services-extended-support/overview.md). This separate service offering ensures continued assistance and support. Cloud Services Extended Support requires a distinct enrollment and isn't automatically included with existing Azure Cloud Services subscriptions. 
+
+## Next steps
+
+Review the latest [Guest OS releases](cloud-services-guestos-update-matrix.md).

articles/cloud-services/cloud-services-guestos-family-2-3-4-retirement.md

@@ -84,16 +84,20 @@
         href: cloud-services-python-how-to-use-service-management.md
       - name: Mitigating speculative execution
         href: mitigate-se.md
-      - name: Guest OS patches
-        href: cloud-services-guestos-msrc-releases.md
-      - name: Guest OS retirement
+      - name: Guest OS
         items:
-        - name: Retirement policy
-          href: cloud-services-guestos-retirement-policy.md
-        - name: Family 1 retirement notice
-          href: cloud-services-guestos-family1-retirement.md
-      - name: Guest OS release news
-        href: cloud-services-guestos-update-matrix.md
+        - name: Guest OS patches
+          href: cloud-services-guestos-msrc-releases.md
+        - name: Guest OS retirement
+          items:
+          - name: Retirement policy
+            href: cloud-services-guestos-retirement-policy.md
+          - name: Family 1 retirement notice
+            href: cloud-services-guestos-family1-retirement.md
+          - name: Family 2, 3, 4 retirement notice
+            href: cloud-services-guestos-family-2-3-4-retirement.md
+        - name: Guest OS release news
+          href: cloud-services-guestos-update-matrix.md
       - name: Cloud Services Role config XPath cheat sheet
         href: cloud-services-role-config-xpath.md
     - name: Manage certificates

articles/cloud-services/toc.yml

@@ -17,20 +17,20 @@ To get meaningful insights on your Azure Cosmos DB data, you may need to query a
 
 To isolate transactional workloads from the performance impact of complex analytical queries, database data is ingested nightly to a central location using complex Extract-Transform-Load (ETL) pipelines. Such ETL-based analytics are complex, costly with delayed insights on business data.
 
-Azure Cosmos DB addresses these challenges by providing no-ETL, cost-effective analytics offerings. 
+Azure Cosmos DB addresses these challenges by providing zero ETL, cost-effective analytics offerings. 
 
-## No-ETL, near real-time analytics on Azure Cosmos DB
-Azure Cosmos DB offers no-ETL, near real-time analytics on your data without affecting the performance of your transactional workloads or request units (RUs). These offerings remove the need for complex ETL pipelines, making your Azure Cosmos DB data seamlessly available to analytics engines. With reduced latency to insights, you can provide enhanced customer experience and react more quickly to changes in market conditions or business environment. Here are some sample [scenarios](synapse-link-use-cases.md) you can achieve with quick insights into your data. 
+## Zero ETL, near real-time analytics on Azure Cosmos DB
+Azure Cosmos DB offers zero ETL, near real-time analytics on your data without affecting the performance of your transactional workloads or request units (RUs). These offerings remove the need for complex ETL pipelines, making your Azure Cosmos DB data seamlessly available to analytics engines. With reduced latency to insights, you can provide enhanced customer experience and react more quickly to changes in market conditions or business environment. Here are some sample [scenarios](synapse-link-use-cases.md) you can achieve with quick insights into your data. 
 
- You can enable no-ETL analytics and BI reporting on Azure Cosmos DB using the following options:
+ You can enable zero-ETL analytics and BI reporting on Azure Cosmos DB using the following options:
 
 * Mirroring your data into Microsoft Fabric
 * Enabling Azure Synapse Link to access data from Azure Synapse Analytics
 
 
 ### Option 1: Mirroring your Azure Cosmos DB data into Microsoft Fabric
 
-Mirroring enables you to seamlessly bring your Azure Cosmos DB database data into Microsoft Fabric. With no-ETL, you can get rich business insights on your Azure Cosmos DB data using Fabric’s built-in analytics, BI, and AI capabilities.
+Mirroring enables you to seamlessly bring your Azure Cosmos DB database data into Microsoft Fabric. With zero ETL, you can get quick, rich business insights on your Azure Cosmos DB data using Fabric’s built-in analytics, BI, and AI capabilities.
 
 Your Cosmos DB operational data is incrementally replicated into Fabric OneLake in near real-time. Data in OneLake is stored in open-source Delta Parquet format and made available to all analytical engines in Fabric. With open access, you can use it with various Azure services such as Azure Databricks, Azure HDInsight, and more. OneLake also helps unify your data estate for your analytical needs. Mirrored data can be joined with any other data in OneLake, such as Lakehouses, Warehouses or shortcuts. You can also join Azure Cosmos DB data with other mirrored database sources such as Azure SQL Database, Snowflake.
 You can query across Azure Cosmos DB collections or databases mirrored into OneLake. 
@@ -41,7 +41,7 @@ You can use T-SQL to run complex aggregate queries and Spark for data exploratio
 :::image type="content" source="./media/analytics-and-bi/fabric-mirroring-cosmos-db.png" alt-text="Diagram of Azure Cosmos DB mirroring in Microsoft Fabric." border="false":::
 
 If you're looking for analytics on your operational data in Azure Cosmos DB, mirroring provides:
-* No-ETL, cost-effective near real-time analytics on Azure Cosmos DB data without affecting your request unit (RU) consumption
+* Zero ETL, cost-effective near real-time analytics on Azure Cosmos DB data without affecting your request unit (RU) consumption
 * Ease of bringing data across various sources into Fabric OneLake.
 * Improved query performance of SQL engine handling delta tables, with V-order optimizations
 * Improved cold start time for Spark engine with deep integration with ML/notebooks
@@ -53,7 +53,7 @@ To get started with mirroring, visit ["Get started with mirroring tutorial"](/fa
 
 
 ### Option 2: Azure Synapse Link to access data from Azure Synapse Analytics
-Azure Synapse Link for Azure Cosmos DB creates a tight seamless integration between Azure Cosmos DB and Azure Synapse Analytics, enabling no-ETL, near real-time analytics on your operational data. 
+Azure Synapse Link for Azure Cosmos DB creates a tight seamless integration between Azure Cosmos DB and Azure Synapse Analytics, enabling zero ETL, near real-time analytics on your operational data. 
 Transactional data is seamlessly synced to Analytical store, which stores the data in columnar format optimized for analytics. 
 
 Azure Synapse Analytics can access this data in Analytical store, without further movement, using Azure Synapse Link. Business analysts, data engineers, and data scientists can now use Synapse Spark or Synapse SQL interchangeably to run near real time business intelligence, analytics, and machine learning pipelines. 
@@ -82,7 +82,7 @@ While these options are included for completeness and work well with single part
 
   When analytical queries are run directly against your database or collections, they increase the need for request units allocated, as analytical queries tend to be complex and need more computation power. Increased RU usage will likely lead to significant cost impact over time, if you run aggregate queries. 
 
-Instead of these options, we recommend that you use Mirroring in Microsoft Fabric or Azure Synapse Link, which provide no-ETL analytics, without affecting transactional workload performance or request units.
+Instead of these options, we recommend that you use Mirroring in Microsoft Fabric or Azure Synapse Link, which provide zero ETL analytics, without affecting transactional workload performance or request units.
 
 ## Related content