Merge pull request #8891 from MicrosoftDocs/main

Auto Publish – main to live - 2026-04-16 23:00 UTC

Author: learn-build-service-prod[bot]

articles/java/migration/migrate-github-copilot-app-modernization-for-java-quickstart-chat-window.md

@@ -50,7 +50,7 @@ With the AppModernization agent selected, use simple, natural language prompts t
 
 1. In the Copilot chat window with the AppModernization agent selected, enter the following prompt:
 
-   ```
+   ```prompt
    migrate from rabbitmq to Azure service bus
    ```
 
@@ -62,31 +62,31 @@ The AppModernization agent supports various migration scenarios with simple prom
 
 - **Database migration**:
 
-  ```
+  ```prompt
   migrate from Oracle to Azure PostgreSQL
   ```
 
 - **Authentication migration**:
 
-  ```
+  ```prompt
   migrate to Managed Identity for Azure SQL Database
   ```
 
 - **Storage migration**:
 
-  ```
+  ```prompt
   migrate from AWS S3 to Azure Storage Blob
   ```
 
 - **Messaging migration**:
 
-  ```
+  ```prompt
   migrate from ActiveMQ to Azure Service Bus
   ```
 
 - **Secret management**:
 
-  ```
+  ```prompt
   migrate secrets to Azure Key Vault
   ```
 

articles/java/sdk/lro.md

@@ -27,7 +27,7 @@ Both `SyncPoller` and `PollerFlux` are the client-side abstractions intended to
 Calling any API that returns a `SyncPoller` will immediately start the long-running operation. The API will return the `SyncPoller` immediately, letting you monitor the progress of the long-running operation and retrieve the final result. The following example shows how to monitor the progress of a long-running operation using the `SyncPoller`.
 
 ```java
-SyncPoller<UploadBlobProgress, UploadedBlobProperties> poller = syncClient.beginUploadFromUri(<URI to upload from>)
+SyncPoller<UploadBlobProgress, UploadedBlobProperties> poller = syncClient.beginUploadFromUri(<URI to upload from>);
 PollResponse<UploadBlobProgress> response;
 
 do {

articles/java/sdk/pagination.md

@@ -74,7 +74,7 @@ Iterable<PagedResponse<Secret>> secretPages = client.listSecrets().iterableByPag
 for (PagedResponse<Secret> page : secretPages) {
    System.out.println("Response code: " + page.getStatusCode());
    System.out.println("Continuation Token: " + page.getContinuationToken());
-   page.getElements().forEach(secret -> System.out.println("Secret value: " + secret))
+   page.getElements().forEach(secret -> System.out.println("Secret value: " + secret));
 }
 ```
 
@@ -90,7 +90,7 @@ client.listSecrets()
       .forEach(page -> {
           System.out.println("Response code: " + page.getStatusCode());
           System.out.println("Continuation Token: " + page.getContinuationToken());
-          page.getElements().forEach(secret -> System.out.println("Secret value: " + secret))
+          page.getElements().forEach(secret -> System.out.println("Secret value: " + secret));
       });
 ```
 
@@ -118,7 +118,7 @@ asyncClient.listSecrets().byPage()
     .subscribe(page -> {
             System.out.println("Response code: " + page.getStatusCode());
             System.out.println("Continuation Token: " + page.getContinuationToken());
-            page.getElements().forEach(secret -> System.out.println("Secret value: " + secret))
+            page.getElements().forEach(secret -> System.out.println("Secret value: " + secret));
         },
         ex -> System.out.println("Error listing pages with secret: " + ex.getMessage()),
         () -> System.out.println("Successfully listed all pages with secret"));

articles/java/spring-framework/spring-cloud-stream-support.md

@@ -757,7 +757,7 @@ spring:
         subscription-id: ${AZURE_SUBSCRIPTION_ID}
       eventhubs:
         resource:
-          resource-group: ${AZURE_EVENTHUBS_RESOURECE_GROUP}
+          resource-group: ${AZURE_EVENTHUBS_RESOURCE_GROUP}
 ```
 
 > [!NOTE]
@@ -899,99 +899,99 @@ The above [connection](#connection-configuration-properties-1) and [common Azure
 
    * For credentials as connection string, configure the following properties in your **application.yml** file:
 
-     ```yaml
-         spring:
-           cloud:
-             azure:
-               servicebus:
-                 connection-string: ${SERVICEBUS_NAMESPACE_CONNECTION_STRING}
-             function:
-               definition: consume;supply
-             stream:
-               bindings:
-                 consume-in-0:
-                   destination: ${SERVICEBUS_ENTITY_NAME}
-                   # If you use Service Bus Topic, add the following configuration
-                   # group: ${SUBSCRIPTION_NAME}
-                 supply-out-0:
-                   destination: ${SERVICEBUS_ENTITY_NAME_SAME_AS_ABOVE}
-               servicebus:
-                 bindings:
-                   consume-in-0:
-                     consumer:
-                       auto-complete: false
-                   supply-out-0:
-                     producer:
-                       entity-type: queue # set as "topic" if you use Service Bus Topic
+      ```yaml
+      spring:
+        cloud:
+          azure:
+            servicebus:
+              connection-string: ${SERVICEBUS_NAMESPACE_CONNECTION_STRING}
+          function:
+            definition: consume;supply
+          stream:
+            bindings:
+              consume-in-0:
+                destination: ${SERVICEBUS_ENTITY_NAME}
+                # If you use Service Bus Topic, add the following configuration
+                # group: ${SUBSCRIPTION_NAME}
+              supply-out-0:
+                destination: ${SERVICEBUS_ENTITY_NAME_SAME_AS_ABOVE}
+            servicebus:
+              bindings:
+                consume-in-0:
+                  consumer:
+                    auto-complete: false
+                supply-out-0:
+                  producer:
+                    entity-type: queue # set as "topic" if you use Service Bus Topic
      ```
 
      [!INCLUDE [security-note](../includes/security-note.md)]
 
    * For credentials as service principal, configure the following properties in your **application.yml** file:
 
-     ```yaml
-         spring:
-           cloud:
-             azure:
-               credential:
-                 client-id: ${AZURE_CLIENT_ID}
-                 client-secret: ${AZURE_CLIENT_SECRET}
-               profile:
-                 tenant-id: <tenant>
-               servicebus:
-                 namespace: ${SERVICEBUS_NAMESPACE}
-             function:
-               definition: consume;supply
-             stream:
-               bindings:
-                 consume-in-0:
-                   destination: ${SERVICEBUS_ENTITY_NAME}
-                   # If you use Service Bus Topic, add the following configuration
-                   # group: ${SUBSCRIPTION_NAME}
-                 supply-out-0:
-                   destination: ${SERVICEBUS_ENTITY_NAME_SAME_AS_ABOVE}
-               servicebus:
-                 bindings:
-                   consume-in-0:
-                     consumer:
-                       auto-complete: false
-                   supply-out-0:
-                     producer:
-                       entity-type: queue # set as "topic" if you use Service Bus Topic
+      ```yaml
+      spring:
+        cloud:
+          azure:
+            credential:
+              client-id: ${AZURE_CLIENT_ID}
+              client-secret: ${AZURE_CLIENT_SECRET}
+            profile:
+              tenant-id: <tenant>
+            servicebus:
+              namespace: ${SERVICEBUS_NAMESPACE}
+          function:
+            definition: consume;supply
+          stream:
+            bindings:
+              consume-in-0:
+                destination: ${SERVICEBUS_ENTITY_NAME}
+                # If you use Service Bus Topic, add the following configuration
+                # group: ${SUBSCRIPTION_NAME}
+              supply-out-0:
+                destination: ${SERVICEBUS_ENTITY_NAME_SAME_AS_ABOVE}
+            servicebus:
+              bindings:
+                consume-in-0:
+                  consumer:
+                    auto-complete: false
+                supply-out-0:
+                  producer:
+                    entity-type: queue # set as "topic" if you use Service Bus Topic
      ```
 
 > [!NOTE]
 > The values allowed for `tenant-id` are: `common`, `organizations`, `consumers`, or the tenant ID. For more information about these values, see the [Used the wrong endpoint (personal and organization accounts)](/troubleshoot/azure/active-directory/error-code-aadsts50020-user-account-identity-provider-does-not-exist#cause-3-used-the-wrong-endpoint-personal-and-organization-accounts) section of [Error AADSTS50020 - User account from identity provider does not exist in tenant](/troubleshoot/azure/active-directory/error-code-aadsts50020-user-account-identity-provider-does-not-exist). For information on converting your single-tenant app, see [Convert single-tenant app to multitenant on Microsoft Entra ID](/entra/identity-platform/howto-convert-app-to-be-multi-tenant).
 
    * For credentials as managed identities, configure the following properties in your **application.yml** file:
 
-     ```yaml
-         spring:
-           cloud:
-             azure:
-               credential:
-                 managed-identity-enabled: true
-                 client-id: ${MANAGED_IDENTITY_CLIENT_ID} # Only needed when using a user-assigned managed identity
-               servicebus:
-                 namespace: ${SERVICEBUS_NAMESPACE}
-             function:
-               definition: consume;supply
-             stream:
-               bindings:
-                 consume-in-0:
-                   destination: ${SERVICEBUS_ENTITY_NAME}
-                   # If you use Service Bus Topic, add the following configuration
-                   # group: ${SUBSCRIPTION_NAME}
-                 supply-out-0:
-                   destination: ${SERVICEBUS_ENTITY_NAME_SAME_AS_ABOVE}
-               servicebus:
-                 bindings:
-                   consume-in-0:
-                     consumer:
-                       auto-complete: false
-                   supply-out-0:
-                     producer:
-                       entity-type: queue # set as "topic" if you use Service Bus Topic
+      ```yaml
+      spring:
+        cloud:
+          azure:
+            credential:
+              managed-identity-enabled: true
+              client-id: ${MANAGED_IDENTITY_CLIENT_ID} # Only needed when using a user-assigned managed identity
+            servicebus:
+              namespace: ${SERVICEBUS_NAMESPACE}
+          function:
+            definition: consume;supply
+          stream:
+            bindings:
+              consume-in-0:
+                destination: ${SERVICEBUS_ENTITY_NAME}
+                # If you use Service Bus Topic, add the following configuration
+                # group: ${SUBSCRIPTION_NAME}
+              supply-out-0:
+                destination: ${SERVICEBUS_ENTITY_NAME_SAME_AS_ABOVE}
+            servicebus:
+              bindings:
+                consume-in-0:
+                  consumer:
+                    auto-complete: false
+                supply-out-0:
+                  producer:
+                    entity-type: queue # set as "topic" if you use Service Bus Topic
      ```
 
 1. Define supplier and consumer.
@@ -1392,7 +1392,7 @@ spring:
         subscription-id: ${AZURE_SUBSCRIPTION_ID}
       servicebus:
         resource:
-          resource-group: ${AZURE_SERVICEBUS_RESOURECE_GROUP}
+          resource-group: ${AZURE_SERVICEBUS_RESOURCE_GROUP}
     stream:
       servicebus:
         bindings:

articles/java/spring-framework/spring-integration-support.md

@@ -254,7 +254,7 @@ developers can use `EventHubsContainerProperties` for the configuration. See [th
        public EventHubsInboundChannelAdapter messageChannelAdapter(
                @Qualifier(INPUT_CHANNEL) MessageChannel inputChannel,
                EventHubsMessageListenerContainer listenerContainer) {
-           EventHubsInboundChannelAdapter adapter = new EventHubsInboundChannelAdapter(processorContainer);
+           EventHubsInboundChannelAdapter adapter = new EventHubsInboundChannelAdapter(listenerContainer);
            adapter.setOutputChannel(inputChannel);
            return adapter;
        }
@@ -307,7 +307,7 @@ class Demo {
     public EventHubsInboundChannelAdapter messageChannelAdapter(
             @Qualifier(INPUT_CHANNEL) MessageChannel inputChannel,
             EventHubsMessageListenerContainer listenerContainer) {
-        EventHubsInboundChannelAdapter adapter = new EventHubsInboundChannelAdapter(processorContainer, ListenerMode.BATCH);
+        EventHubsInboundChannelAdapter adapter = new EventHubsInboundChannelAdapter(listenerContainer, ListenerMode.BATCH);
         adapter.setOutputChannel(inputChannel);
         return adapter;
     }
@@ -488,7 +488,7 @@ developers can use `ServiceBusContainerProperties` for the configuration. See [t
 
                @Override
                public void onFailure(Throwable ex) {
-                   LOGGER.info("There was an error sending the message.");
+                   LOGGER.error("There was an error sending the message.", ex);
                }
            });
 
@@ -808,7 +808,7 @@ Connection configurable properties of `spring-cloud-azure-starter-integration-st
 
                @Override
                public void onFailure(Throwable ex) {
-                   LOGGER.info("There was an error sending the message.");
+                   LOGGER.error("There was an error sending the message.", ex);
                }
            });
            return handler;

articles/java/spring-framework/spring-security-support.md

@@ -507,14 +507,14 @@ Then you can use `OAuth2AuthorizedClient` in application like this
 public class Demo {
     @GetMapping("/resource-server-1")
     @ResponseBody
-    public String graph(
+    public String graph1(
     @RegisteredOAuth2AuthorizedClient("resource-server-1") OAuth2AuthorizedClient client) {
         return callResourceServer1(client);
     }
 
     @GetMapping("/resource-server-2")
     @ResponseBody
-    public String graph(
+    public String graph2(
     @RegisteredOAuth2AuthorizedClient("resource-server-2") OAuth2AuthorizedClient client) {
         return callResourceServer2(client);
     }
@@ -1352,7 +1352,7 @@ public class WebSecurityConfiguration extends WebSecurityConfigurerAdapter {
    private final AadB2cOidcLoginConfigurer configurer;
 
    public WebSecurityConfiguration(AadB2cOidcLoginConfigurer configurer) {
-       this.configurer == configurer;
+       this.configurer = configurer;
    }
 
    @Override
@@ -1362,7 +1362,7 @@ public class WebSecurityConfiguration extends WebSecurityConfigurerAdapter {
                .anyRequest().authenticated()
                .and()
            .apply(configurer);
-       // @formatter:off
+       // @formatter:on
    }
 }
 ```

articles/rust/sdk/use-crates.md

@@ -70,7 +70,7 @@ The code shown in this article is available on <https://github.com/azure-samples
 
 [Azure SDK main Cargo.toml]: https://github.com/Azure/azure-sdk-for-rust/blob/main/Cargo.toml
 
-[Ref doc - secret - SecretClient]: https://docs.rs/azure_security_keyvault_secrets/latest/azure_security_keyvault_secrets/struct.SecretClient.html
+[Ref doc - secret - SecretClient]: https://docs.rs/azure_security_keyvault_secrets/latest/azure_security_keyvault_secrets/
 [Ref doc - core - ClientOptions]:https://docs.rs/azure_core/latest/azure_core/http/struct.ClientOptions.html
 [Ref doc - core - Response]: https://docs.rs/azure_core/latest/azure_core/http/response/struct.Response.html
 [Ref doc - core - http status code]: https://docs.rs/azure_core/latest/azure_core/http/enum.StatusCode.html