Merge pull request #290940 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: Taojunshen

articles/azure-app-configuration/concept-key-value.md

@@ -96,7 +96,7 @@ Each key-value in App Configuration has a content type attribute. You can option
 > [!div class="nextstepaction"]
 > [Point-in-time snapshot](./concept-point-time-snapshot.md)
 
-> [!div class="neSxtstepaction"]
+> [!div class="nextstepaction"]
 > [Feature management](./concept-feature-management.md)
 
 > [!div class="nextstepaction"]

articles/event-hubs/event-hubs-capture-enable-through-portal.md

@@ -11,12 +11,12 @@ ms.custom: mode-ui
 Azure [Event Hubs Capture][capture-overview] enables you to automatically deliver the streaming data in Event Hubs to an [Azure Blob storage](https://azure.microsoft.com/services/storage/blobs/) or [Azure Data Lake Storage Gen 2](https://azure.microsoft.com/services/data-lake-store/) account of your choice. You can configure capture settings using the [Azure portal](https://portal.azure.com) when creating an event hub or for an existing event hub. For conceptual information on this feature, see [Event Hubs Capture overview][capture-overview].
 
 > [!IMPORTANT]
-> Event Hubs doesn't support capturing events in a **premium** storage account. 
+> Event Hubs only supports **Premium** Storage account with **Block Blob** support. 
 
 
 ## Enable Capture when you create an event hub
 
-If you don't have an Event Hubs namespace to work with, create a **standard** tier namespace by following steps from the article: [Create an Event Hubs namespace](event-hubs-create.md#create-an-event-hubs-namespace). Make sure that you select **Standard** for the **pricing tier**. The basic tier doesn't support the Capture feature. 
+If you don't have an Event Hubs namespace to work with, create a namespace by following steps from the article: [Create an Event Hubs namespace](event-hubs-create.md#create-an-event-hubs-namespace). Make sure that you select **Standard** or higher **pricing tier**. The basic tier doesn't support the Capture feature. 
 
 To create an event hub within the namespace, follow these steps:
 

articles/sentinel/notebooks-hunt.md

@@ -148,7 +148,7 @@ If you have multiple notebooks, make sure to select a default AML workspace to u
 
 ## Launch a notebook in your Azure Machine Learning workspace
 
-After you create an Azure Machine Learning workspace, launch your notebook in that workspace from Microsoft Sentinel. Be aware that if you have private endpoints enabled in your Azure storage account, you can't launch notebooks in the Azure Machine Learning workspace from Microsoft Sentinel. You must copy the notebook template from Microsoft Sentinel and upload the notebook to the Azure Machine Learning studio.
+After you create an Azure Machine Learning workspace, launch your notebook in that workspace from Microsoft Sentinel. Be aware that if you have private endpoints or restrictions on the public network access enabled in your Azure storage account, you can't launch notebooks in the Azure Machine Learning workspace from Microsoft Sentinel. You must copy the notebook template from Microsoft Sentinel and upload the notebook to the Azure Machine Learning studio.
 
 To launch your Microsoft Sentinel notebook in your Azure Machine Learning workspace, complete the following steps. 
 

articles/sentinel/unified-connector-cef-device.md

@@ -182,6 +182,22 @@ Set your security solution to send syslog messages in CEF format to the proxy ma
 
 In ForgeRock, install and configure this Common Audit (CAUD) for Microsoft Sentinel per the documentation at https://github.com/javaservlets/SentinelAuditEventHandler. Next, in Azure, follow the steps to configure the CEF via AMA data connector.
 
+## Fortinet
+
+Set your Fortinet to send Syslog messages in CEF format to the proxy machine. Make sure you send the logs to port 514 TCP on the machine's IP address.<br/>
+
+Copy the CLI commands below and:
+
+-   Replace \"server &lt;ip address&gt;\" with the Syslog agent's IP address.<br/>
+-   Set the \"&lt;facility_name&gt;\" to use the facility you configured in the Syslog agent (by default, the agent sets this to local4).<br/>
+-   Set the Syslog port to 514, the port your agent uses.<br/>
+-   To enable CEF format in early FortiOS versions, you may need to run the command \"set csv disable\".<br/>For more information, go to the  [Fortinet Document Library](https://aka.ms/asi-syslog-fortinet-fortinetdocumentlibrary), choose your version, and use the \"Handbook\" and \"Log Message Reference\" PDFs.<br/>
+
+[Learn more >](https://aka.ms/CEF-Fortinet)
+
+Set up the connection using the CLI to run the following commands:
+`config log syslogd setting/n    set status enable/nset format cef/nset port 514/nset server <ip_address_of_Receiver>/nend`
+
 ## iboss
 
 Set your Threat Console to send syslog messages in CEF format to your Azure workspace. Make note of your **Workspace ID** and **Primary Key** within your Log Analytics workspace. Select the workspace from the Log Analytics workspaces menu in the Azure portal. Then select **Agents management** in the **Settings** section. 

articles/service-bus-messaging/service-bus-troubleshooting-guide.md

@@ -20,7 +20,7 @@ To troubleshoot:
 - Try using the Web Socket transport option, which connects using port 443. For details, see [configure the transport](https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/servicebus/Azure.Messaging.ServiceBus/samples/Sample13_AdvancedConfiguration.md#configuring-the-transport).
 - See if your network is blocking specific IP addresses. For details, see [What IP addresses do I need to allow?](/azure/service-bus-messaging/service-bus-faq#what-ip-addresses-do-i-need-to-add-to-allowlist-)
 - If applicable, verify the proxy configuration. For details, see: [Configuring the transport](https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/servicebus/Azure.Messaging.ServiceBus/samples/Sample13_AdvancedConfiguration.md#configuring-the-transport)
-- For more information about troubleshooting network connectivity, see: [Connectivity, certificate, or timeout issues][#connectivity-certificate-or-timeout-issues].
+- For more information about troubleshooting network connectivity, see: [Connectivity, certificate, or timeout issues](#connectivity-certificate-or-timeout-issues).
 
 ### Secure socket layer (SSL) handshake failures
 This error can occur when an intercepting proxy is used. To verify, We recommend that you test the application in the host environment with the proxy disabled.
@@ -289,4 +289,12 @@ See the following articles:
 [MessageBody]: https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/servicebus/Azure.Messaging.ServiceBus/samples/Sample14_AMQPMessage.md#message-body
 [MaxConcurrentSessions]: /dotnet/api/azure.messaging.servicebus.servicebussessionprocessoroptions.maxconcurrentsessions
 [DebugThreadPoolStarvation]: /dotnet/core/diagnostics/debug-threadpool-starvation
-[DiagnoseThreadPoolExhaustion]: /shows/on-net/diagnosing-thread-pool-exhaustion-issues-in-net-core-apps
+[DiagnoseThreadPoolExhaustion]: /shows/on-net/diagnosing-thread-pool-exhaustion-issues-in-net-core-apps
+[TryTimeout]: https://learn.microsoft.com/dotnet/api/azure.messaging.servicebus.servicebusretryoptions.trytimeout?view=azure-dotnet
+[SessionIdleTimeout]: https://learn.microsoft.com/dotnet/api/azure.messaging.servicebus.servicebussessionprocessoroptions.sessionidletimeout?view=azure-dotnet
+[BackgroundService]: https://learn.microsoft.com/dotnet/api/microsoft.extensions.hosting.backgroundservice?view=dotnet
+[TransactionTimeout]: https://learn.microsoft.com/azure/service-bus-messaging/service-bus-transactions#timeout
+[CrossEntityTransactions]: https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/servicebus/Azure.Messaging.ServiceBus/samples/Sample06_Transactions.md#transactions-across-entities
+[Transactions]: https://learn.microsoft.com/azure/service-bus-messaging/service-bus-transactions
+[TransactionOperations]: https://learn.microsoft.com/azure/service-bus-messaging/service-bus-transactions#operations-within-a-transaction-scope
+[ServiceBusQuotas]: https://learn.microsoft.com/azure/service-bus-messaging/service-bus-quotas