Merge pull request #278829 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: rmca14

articles/aks/learn/quick-kubernetes-deploy-terraform.md

@@ -49,7 +49,7 @@ Azure Kubernetes Service (AKS) is a managed Kubernetes service that lets you qui
 
 First, log into your Azure account and authenticate using one of the methods described in the following section.
 
-[!INCLUDE [authenticate-to-azure.md](~/azure-dev-docs-pr/articles/terraform/includes/authenticate-to-azure.md)]
+Terraform only supports authenticating to Azure with the Azure CLI. Authenticating using Azure PowerShell isn't supported. Therefore, while you can use the Azure PowerShell module when doing your Terraform work, you first need to [authenticate to Azure](/azure/developer/terraform/authenticate-to-azure).  
 
 ## Implement the Terraform code
 

articles/azure-arc/servers/troubleshoot-extended-security-updates.md

@@ -66,7 +66,7 @@ Ensure that both the licensing package and servicing stack update (SSU) are down
 If installing the Extended Security Update enabled by Azure Arc fails with errors such as "ESU: Trying to Check IMDS Again LastError=HRESULT_FROM_WIN32(12029)" or "ESU: Trying to Check IMDS Again LastError=HRESULT_FROM_WIN32(12002)", you may need to update the intermediate certificate authorities trusted by your computer using one of the following methods.
 
 > [!IMPORTANT]
-> If you're running the [latest version of the Azure Connected machine agent](agent-release-notes.md), it's not necessary to install the intermediate CA certificates or allow access to the PKI URL.
+> If you're running the [latest version of the Azure Connected machine agent](agent-release-notes.md), it's not necessary to install the intermediate CA certificates or allow access to the PKI URL. However, if a license was already assigned before the agent was upgraded, it can take up to 15 days for the older license to be replaced. During this time, the intermediate cert will still be required. After upgrading the agent, you can delete the license file `%ProgramData%\AzureConnectedMachineAgent\certs\license.json` to force it to be refreshed.
 
 #### Option 1: Allow access to the PKI URL
 

articles/backup/quick-kubernetes-backup-terraform.md

@@ -67,7 +67,7 @@ Things to ensure before you configure AKS backup:
 
 Log in to your Azure account and authenticate using one of the following methods:
 
-[!INCLUDE [authenticate-to-azure.md](~/azure-dev-docs-pr/articles/terraform/includes/authenticate-to-azure.md)]
+Terraform only supports authenticating to Azure with the Azure CLI. Authenticating using Azure PowerShell isn't supported. Therefore, while you can use the Azure PowerShell module when doing your Terraform work, you first need to [authenticate to Azure](/azure/developer/terraform/authenticate-to-azure).
 
 ## Implement the Terraform code
 

articles/firewall/features.md

@@ -49,7 +49,7 @@ Azure Firewall can be configured during deployment to span multiple Availability
 
 You can also associate Azure Firewall to a specific zone just for proximity reasons, using the service standard 99.95% SLA.
 
-There's no extra cost for a firewall deployed in more than one Availability Zone. However, there are added costs for inbound and outbound data transfers associated with Availability Zones. For more information, see [Bandwidth pricing details](https://azure.microsoft.com/pricing/details/bandwidth/).
+There's no extra cost for a firewall deployed in more than one Availability Zone. Also, Microsoft has announced that Azure won't charge for the data transfer across availability zones, regardless of whether you use private or public IPs on your [Azure resources](https://azure.microsoft.com/updates/update-on-interavailability-zone-data-transfer-pricing/).
 
 As the firewall scales, it creates instances in the zones it's in. So, if the firewall is in Zone 1 only, new instances are created in Zone 1. If the firewall is in all three zones, then it creates instances across the three zones as it scales.
 

articles/service-bus-messaging/build-message-driven-apps-nservicebus.md

@@ -32,10 +32,10 @@ The sample assumes you've [created an Azure Service Bus namespace](service-bus-q
     The following diagram, generated by [ServiceInsight](https://particular.net/serviceinsight), a visualization and debugging tool from Particular Software, shows the message flow:
 
     :::image type="content" source="./media/nservicebus/sequence-diagram.png" alt-text="Image showing the sequence diagram":::    
-1. Open `SendReceiveWithNservicebus.sln` in your favorite code editor (For example, Visual Studio 2019). 
+1. Open `SendReceiveWithNservicebus.sln` in your favorite code editor (For example, Visual Studio 2022). 
 1. Open `appsettings.json` in both the Receiver and Sender projects and set `AzureServiceBusConnectionString` to the connection string for your Azure Service Bus namespace.
-
-
+   - This can be found in the Azure portal under  **Service Bus Namespace** > **Settings** > **Shared access policies** > **RootManageSharedAccessKey** > **Primary Connection String** .
+   - The `AzureServiceBusTransport` also has a constructor that accepts a namespace and token credential, which in a production environment will be more secure, however for the purposes of this tutorial the shared access key connection string will be used.
 
 ## Define the shared message contracts
 
@@ -86,14 +86,15 @@ var host = Host.CreateDefaultBuilder(args)
         // Configure the NServiceBus endpoint
         var endpointConfiguration = new EndpointConfiguration("Sender");
 
-        var transport = endpointConfiguration.UseTransport<AzureServiceBusTransport>();
         var connectionString = context.Configuration.GetConnectionString("AzureServiceBusConnectionString");
-        transport.ConnectionString(connectionString);
+        // If token credentials are to be used, the overload constructor for AzureServiceBusTransport would be used here
+        var routing = endpointConfiguration.UseTransport(new AzureServiceBusTransport(connectionString));
+        endpointConfiguration.UseSerialization<SystemJsonSerializer>();
 
-        transport.Routing().RouteToEndpoint(typeof(Ping), "Receiver");
+        endpointConfiguration.AuditProcessedMessagesTo("audit");
+        routing.RouteToEndpoint(typeof(Ping), "Receiver");
 
         endpointConfiguration.EnableInstallers();
-        endpointConfiguration.AuditProcessedMessagesTo("audit");
 
         return endpointConfiguration;
     })
@@ -140,13 +141,11 @@ public class SenderWorker : BackgroundService
             var round = 0;
             while (!stoppingToken.IsCancellationRequested)
             {
-                await messageSession.Send(new Ping { Round = round++ })
-                    .ConfigureAwait(false);
+                await messageSession.Send(new Ping { Round = round++ });;
 
                 logger.LogInformation($"Message #{round}");
 
-                await Task.Delay(1_000, stoppingToken)
-                    .ConfigureAwait(false);
+                await Task.Delay(1_000, stoppingToken);
             }
         }
         catch (OperationCanceledException)
@@ -204,11 +203,10 @@ Let's ignore the commented code for now; we'll get back to it later when we talk
 
 The class implements `IHandleMessages<Ping>`, which defines one method: `Handle`. This interface tells NServiceBus that when the endpoint receives a message of type `Ping`, it should be processed by the `Handle` method in this handler. The `Handle` method takes the message itself as a parameter, and an `IMessageHandlerContext`, which allows further messaging operations, such as replying, sending commands, or publishing events.
 
-Our `PingHandler` is straightforward: when a `Ping` message is received, log the message details and reply back to the sender with a new `Pong` message.
+Our `PingHandler` is straightforward: when a `Ping` message is received, log the message details and reply back to the sender with a new `Pong` message, which is subsequently handled in the Sender's `PongHandler`.
 
 > [!NOTE]
 > In the Sender's configuration, you specified that `Ping` messages should be routed to the Receiver. NServiceBus adds metadata to the messages indicating, among other things, the origin of the message. This is why you don't need to specify any routing data for the `Pong` reply message; it's automatically routed back to its origin: the Sender.
->
 
 With the Sender and Receiver both properly configured, you can now run the solution.
 
@@ -301,21 +299,20 @@ Next, it's time to figure out where to deploy our solution in Azure.
 In this sample, the Sender and Receiver endpoints are configured to run as console applications. They can also be hosted in various Azure services including Azure Functions, Azure App Services, Azure Container Instances, Azure Kubernetes Services, and Azure VMs. For example, here's how the Sender endpoint can be configured to run as an Azure Function:
 
 ```csharp
-[assembly: FunctionsStartup(typeof(Startup))]
-[assembly: NServiceBusEndpointName("Sender")]
-
-public class Startup : FunctionsStartup
+[assembly: NServiceBusTriggerFunction("Sender")]
+public class Program
 {
-    public override void Configure(IFunctionsHostBuilder builder)
+    public static async Task Main()
     {
-        builder.UseNServiceBus(() =>
-        {
-            var configuration = new ServiceBusTriggeredEndpointConfiguration("Sender");
-            var transport = configuration.AdvancedConfiguration.Transport;
-            transport.Routing().RouteToEndpoint(typeof(Ping), "Receiver");
+        var host = new HostBuilder()
+            .ConfigureFunctionsWorkerDefaults()
+            .UseNServiceBus(configuration =>
+            {
+                configuration.Routing().RouteToEndpoint(typeof(Ping), "Receiver");
+            })
+            .Build();
 
-            return configuration;
-        });
+        await host.RunAsync();
     }
 }
 ```

articles/service-fabric/service-fabric-versions.md

@@ -20,7 +20,7 @@ If you want to find a list of all the available Service Fabric runtime versions
 ### Current versions
 | Service Fabric runtime |Can upgrade directly from|Can downgrade to*|Compatible SDK or NuGet package version|Supported .NET runtimes** |OS Version |End of support |
 | --- | --- | --- | --- | --- | --- | --- |
-| 10.1 CU3<br>10.1.2175.9590  | 9.1 CU6<br>9.1.1851.9590 | 9.0 | Less than or equal to version 7.1 | .NET 7, .NET 6, All, <br> >= .NET Framework 4.6.2 | [See supported OS version](#supported-windows-versions-and-support-end-date) | Current version |
+| 10.1 CU3<br>10.1.2175.9590  | 9.1 CU6<br>9.1.1851.9590 | 9.0 | Less than or equal to version 7.1 | .NET 8, .NET 7, .NET 6, All, <br> >= .NET Framework 4.6.2 | [See supported OS version](#supported-windows-versions-and-support-end-date) | Current version |
 | 10.1 CU2<br>10.1.1951.9590  | 9.1 CU6<br>9.1.1851.9590 | 9.0 | Less than or equal to version 7.1 | .NET 7, .NET 6, All, <br> >= .NET Framework 4.6.2 | [See supported OS version](#supported-windows-versions-and-support-end-date) | Current version |
 | 10.1 RTO<br>10.1.1541.9590  | 9.1 CU6<br>9.1.1851.9590 | 9.0 | Less than or equal to version 7.1 | .NET 7, .NET 6, All, <br> >= .NET Framework 4.6.2 | [See supported OS version](#supported-windows-versions-and-support-end-date) | Current version |
 | 10.0 CU4<br>10.0.2382.9590 | 9.0 CU10<br>9.0.1553.9590 | 9.0 | Less than or equal to version 7.0 | .NET 7, .NET 6, All, <br> >= .NET Framework 4.6.2 | [See supported OS version](#supported-windows-versions-and-support-end-date) | September 30, 2024 |

articles/virtual-network/virtual-networks-udr-overview.md

@@ -70,7 +70,7 @@ You create custom routes by either creating [user-defined](#user-defined) routes
 
 ### User-defined
 
-You can create custom, or user-defined(static), routes in Azure to override Azure's default system routes, or to add more routes to a subnet's route table. In Azure, you create a route table, then associate the route table to zero or more virtual network subnets. Each subnet can have zero or one route table associated to it. To learn about the maximum number of routes you can add to a route table and the maximum number of user-defined route tables you can create per Azure subscription, see [Azure limits](../azure-resource-manager/management/azure-subscription-service-limits.md?toc=%2fazure%2fvirtual-network%2ftoc.json#networking-limits). When you create a route table and associate it to a subnet, the table's routes are combined with the subnet's default routes. If there are conflicting route assignments, user-defined routes override the default routes.
+To customize your traffic routes, you shouldn't modify the default routes but you should create custom, or user-defined(static) routes which override Azure's default system routes. In Azure, you create a route table, then associate the route table to zero or more virtual network subnets. Each subnet can have zero or one route table associated to it. To learn about the maximum number of routes you can add to a route table and the maximum number of user-defined route tables you can create per Azure subscription, see [Azure limits](../azure-resource-manager/management/azure-subscription-service-limits.md?toc=%2fazure%2fvirtual-network%2ftoc.json#networking-limits). When you create a route table and associate it to a subnet, the table's routes are combined with the subnet's default routes. If there are conflicting route assignments, user-defined routes override the default routes.
 
 You can specify the following next hop types when creating a user-defined route: