Merge pull request #290055 from MicrosoftDocs/main

11/7 11:00 AM IST Publish

Author: PhilKang0704

articles/api-center/set-up-api-center-azure-cli.md

@@ -5,7 +5,7 @@ author: dlepow
 ms.service: azure-api-center
 ms.custom: devx-track-azurecli
 ms.topic: quickstart
-ms.daate: 06/27/2024
+ms.date: 06/27/2024
 ms.author: danlep 
 ---
 

articles/azure-functions/durable/durable-functions-entities.md

@@ -18,7 +18,7 @@ Entity functions define operations for reading and updating small pieces of stat
 Entities provide a means for scaling out applications by distributing the work across many entities, each with a modestly sized state.
 ::: zone pivot="csharp,javascript,python"
 > [!NOTE]
-> Entity functions and related functionality are only available in [Durable Functions 2.0](durable-functions-versions.md#migrate-from-1x-to-2x) and above. They are currently supported in .NET in-proc, .NET isolated worker, JavaScript, and Python, but not in PowerShell or Java.
+> Entity functions and related functionality are only available in [Durable Functions 2.0](durable-functions-versions.md#migrate-from-1x-to-2x) and above. They are currently supported in .NET in-proc, .NET isolated worker, JavaScript, and Python, but not in PowerShell or Java. Furthermore, entity functions for .NET Isolated are supported when using the Azure Storage or Netherite state providers, but not when using the MSSQL state provider.
 ::: zone-end  
 ::: zone pivot="powershell,java"  
 >[!IMPORTANT]

articles/azure-functions/durable/durable-functions-storage-providers.md

@@ -191,6 +191,7 @@ There are many significant tradeoffs between the various supported storage provi
 | Maximum throughput | Moderate | Very high | Moderate |
 | Maximum orchestration/entity scale-out (nodes) | 16 | 32 | N/A |
 | Maximum activity scale-out (nodes) | N/A | 32 | N/A |
+| Durable Entities support | ✅ Fully supported | ✅ Fully supported | ⚠️ Supported except when using .NET Isolated |
 | [KEDA 2.0](https://keda.sh/) scaling support<br/>([more information](../functions-kubernetes-keda.md)) | ❌ Not supported | ❌ Not supported | ✅ Supported using the [MSSQL scaler](https://keda.sh/docs/scalers/mssql/) ([more information](https://microsoft.github.io/durabletask-mssql/#/scaling)) |
 | Support for [extension bundles](../functions-bindings-register.md#extension-bundles) (recommended for non-.NET apps) | ✅ Fully supported | ✅ Fully supported | ✅ Fully supported |
 | Price-performance configurable? | ❌ No | ✅ Yes (Event Hubs TUs and CUs) | ✅ Yes (SQL vCPUs) |

articles/azure-government/azure-secure-isolation-guidance.md

@@ -44,11 +44,11 @@ Microsoft provides [strong customer commitments](https://www.microsoft.com/trust
 
 ## Tenant separation
 
-Azure is a hyperscale public multi-tenant cloud services platform that provides you with access to a feature-rich environment incorporating the latest cloud innovations such as artificial intelligence, machine learning, IoT services, big-data analytics, intelligent edge, and many more to help you increase efficiency and unlock insights into your operations and performance.
+Azure is a hyperscale public multitenant cloud services platform that provides you with access to a feature-rich environment incorporating the latest cloud innovations such as artificial intelligence, machine learning, IoT services, big-data analytics, intelligent edge, and many more to help you increase efficiency and unlock insights into your operations and performance.
 
-A multi-tenant cloud platform implies that multiple customer applications and data are stored on the same physical hardware. Azure uses logical isolation to segregate your applications and data from other customers. This approach provides the scale and economic benefits of multi-tenant cloud services while rigorously helping prevent other customers from accessing your data or applications.
+A multitenant cloud platform implies that multiple customer applications and data are stored on the same physical hardware. Azure uses logical isolation to segregate your applications and data from other customers. This approach provides the scale and economic benefits of multitenant cloud services while rigorously helping prevent other customers from accessing your data or applications.
 
-Azure addresses the perceived risk of resource sharing by providing a trustworthy foundation for assuring multi-tenant, cryptographically certain, logically isolated cloud services using a common set of principles:
+Azure addresses the perceived risk of resource sharing by providing a trustworthy foundation for assuring multitenant, cryptographically certain, logically isolated cloud services using a common set of principles:
 
 - User access controls with authentication and identity separation
 - Compute isolation for processing
@@ -71,7 +71,7 @@ Data encryption provides isolation assurances that are tied directly to encrypti
 
 The [Federal Information Processing Standard (FIPS) 140](https://csrc.nist.gov/publications/detail/fips/140/3/final) is a US government standard that defines minimum security requirements for cryptographic modules in information technology products. Microsoft maintains an active commitment to meeting the [FIPS 140 requirements](/azure/compliance/offerings/offering-fips-140-2), having validated cryptographic modules since the standard’s inception in 2001. Microsoft validates its cryptographic modules under the US National Institute of Standards and Technology (NIST) [Cryptographic Module Validation Program (CMVP)](https://csrc.nist.gov/Projects/cryptographic-module-validation-program). Multiple Microsoft products, including many cloud services, use these cryptographic modules.
 
-While the current CMVP FIPS 140 implementation guidance precludes a FIPS 140 validation for a cloud service, cloud service providers can obtain and operate FIPS 140 validated cryptographic modules for the computing elements that comprise their cloud services. Azure is built with a combination of hardware, commercially available operating systems (Linux and Windows), and Azure-specific version of Windows. Through the Microsoft [Security Development Lifecycle (SDL)](https://www.microsoft.com/securityengineering/sdl/), all Azure services use FIPS 140 approved algorithms for data security because the operating system uses FIPS 140 approved algorithms while operating at a hyper scale cloud. The corresponding crypto modules are FIPS 140 validated as part of the Microsoft [Windows FIPS validation program](/windows/security/threat-protection/fips-140-validation#modules-used-by-windows-server). Moreover, you can store your own cryptographic keys and other secrets in FIPS 140 validated hardware security modules (HSMs) under your control, also known as [customer-managed keys](../security/fundamentals/encryption-models.md#server-side-encryption-using-customer-managed-keys-in-azure-key-vault).
+While the current CMVP FIPS 140 implementation guidance precludes a FIPS 140 validation for a cloud service, cloud service providers can obtain and operate FIPS 140 validated cryptographic modules for the computing elements that comprise their cloud services. Azure is built with a combination of hardware, commercially available operating systems (Linux and Windows), and Azure-specific version of Windows. Through the Microsoft [Security Development Lifecycle (SDL)](https://www.microsoft.com/securityengineering/sdl/), all Azure services use FIPS 140 approved algorithms for data security because the operating system uses FIPS 140 approved algorithms while operating at a hyper scale cloud. The corresponding crypto modules are FIPS 140 validated as part of the Microsoft [Windows FIPS validation program](/windows/security/threat-protection/fips-140-validation#modules-used-by-windows-server). Moreover, you can store your own cryptographic keys and other secrets in FIPS 140 validated hardware security modules (HSMs) under your control, also known as [customer-managed keys](../security/fundamentals/encryption-models.md#server-side-encryption-using-customer-managed-keys-in-azure-key-vault-and-azure-managed-hsm).
 
 ### Encryption key management
 

articles/azure-government/documentation-government-overview-jps.md

@@ -14,7 +14,7 @@ ms.subservice: web-sdk
 
 This document contains information about new features and other changes to the Azure Maps Drawing Tools Module.
 
-## [1.0.5] (CDN: November 4, 2024, npm: TBA)
+## [1.0.5] (CDN: November 4, 2024, npm: November 7)
 
 ### Bug fixes
 
@@ -52,7 +52,7 @@ Stay up to date on Azure Maps:
 > [!div class="nextstepaction"]
 > [Azure Maps Blog]
 
-
+[1.0.5]: https://www.npmjs.com/package/azure-maps-drawing-tools/v/1.0.5
 [1.0.4]: https://www.npmjs.com/package/azure-maps-drawing-tools/v/1.0.4
 [1.0.3]: https://www.npmjs.com/package/azure-maps-drawing-tools/v/1.0.3
 [1.0.2]: https://www.npmjs.com/package/azure-maps-drawing-tools/v/1.0.2

articles/azure-maps/release-notes-drawing-tools-module.md

@@ -16,7 +16,7 @@ This document contains information about new features and other changes to the M
 
 ## v3 (latest)
 
-### [3.5.0] (CDN: November 4, 2024, npm: TBA)
+### [3.5.0] (CDN: November 4, 2024, npm: November 7)
 
 #### New features
 - Add support for fullscreen control.
@@ -640,6 +640,7 @@ Stay up to date on Azure Maps:
 > [!div class="nextstepaction"]
 > [Azure Maps Blog]
 
+[3.5.0]: https://www.npmjs.com/package/azure-maps-control/v/3.5.0
 [3.4.0]: https://www.npmjs.com/package/azure-maps-control/v/3.4.0
 [3.3.0]: https://www.npmjs.com/package/azure-maps-control/v/3.3.0
 [3.2.1]: https://www.npmjs.com/package/azure-maps-control/v/3.2.1

articles/azure-maps/release-notes-map-control.md

@@ -231,7 +231,8 @@ try
             || pollResponse.getStatus() == LongRunningOperationStatus.IN_PROGRESS)
     {
         pollResponse = poller.poll();
-        System.out.println("Email send poller status: " + pollResponse.getStatus());
+        // The operation ID can be retrieved as soon as .poll() is called on the poller
+        System.out.println("Email send poller status: " + pollResponse.getStatus() + ", operation id: " + pollResponse.getValue().getId());
 
         Thread.sleep(POLLER_WAIT_TIME.toMillis());
         timeElapsed = timeElapsed.plus(POLLER_WAIT_TIME);
@@ -262,21 +263,41 @@ catch (Exception exception)
 Calling `beginSend` on the async client returns a `PollerFlux` object to which you can subscribe. The callbacks defined in the subscribe method will be triggered once the email sending opertion is complete. **Note that the initial request to send an email will not be sent until a subscriber is set up.**
 
 ```java
+Duration MAIN_THREAD_WAIT_TIME = Duration.ofSeconds(30);
+
+// ExecutorService to run the polling in a separate thread
+ExecutorService executorService = Executors.newSingleThreadExecutor();
+
 PollerFlux<EmailSendResult, EmailSendResult> poller = emailAsyncClient.beginSend(emailMessage);
-// The initial request is sent out as soon as we subscribe the to PollerFlux object
-poller.subscribe(
+
+executorService.submit(() -> {
+    // The initial request is sent out as soon as we subscribe the to PollerFlux object
+    poller.subscribe(
         response -> {
             if (response.getStatus() == LongRunningOperationStatus.SUCCESSFULLY_COMPLETED) {
-                System.out.printf("Successfully sent the email (operation id: %s)", response.getValue().getId());
+                System.out.printf("Successfully sent the email (operation id: %s)\n", response.getValue().getId());
             }
             else {
-                System.out.println("Email send status: " + response.getStatus());
+                // The operation ID can be retrieved as soon as the first response is recieved from the PollerFlux.
+                System.out.println("Email send status: " + response.getStatus() + ", operation id: " + response.getValue().getId());
             }
         },
         error -> {
             System.out.println("Error occurred while sending email: " + error.getMessage());
         }
-);
+    );
+});
+
+// In a real application, you might have a mechanism to keep the main thread alive.
+// For this sample we will keep the main thread alive for 30 seconds to make sure the child thread has time to recieve the SUCCESSFULLY_COMPLETED status.
+try {
+    Thread.sleep(MAIN_THREAD_WAIT_TIME.toMillis());
+} catch (InterruptedException e) {
+    e.printStackTrace();
+}
+
+executorService.shutdown();
+System.out.println("Main thread ends.");
 ```
 
 ---

articles/communication-services/quickstarts/email/includes/send-email-java.md

@@ -257,6 +257,14 @@ Authorization: Bearer <TOKEN>
 }
 ```
 
+## Logging
+
+Code interpreter sessions don't support logging directly. Your application that's interacting with the sessions can log requests to the session pool management API and its responses.
+
+## Billing
+
+Code interpreter sessions are billed based on the duration of each session. See [Billing](billing.md#dynamic-sessions) for more information.
+
 ## Next steps
 
 > [!div class="nextstepaction"]