Merge pull request #256590 from MicrosoftDocs/main

Publish to live, Monday 4 AM PST, 10/30

Author: ttorble

articles/ai-services/speech-service/includes/quickstarts/openai-speech/csharp.md

@@ -41,7 +41,7 @@ Follow these steps to create a new console application.
     ```
 1. Replace the contents of `Program.cs` with the following code. 
 
-    ```csharp
+ ```csharp
     using System;
     using System.IO;
     using System.Threading.Tasks;
@@ -64,42 +64,67 @@ Follow these steps to create a new console application.
         // This example requires environment variables named "SPEECH_KEY" and "SPEECH_REGION"
         static string speechKey = Environment.GetEnvironmentVariable("SPEECH_KEY");
         static string speechRegion = Environment.GetEnvironmentVariable("SPEECH_REGION");
-    
+
+        // Sentence end symbols for splitting the response into sentences.
+        static List<string> sentenceSaperators = new() { ".", "!", "?", ";", "。", "！", "？", "；", "\n" };
+
+        private static object consoleLock = new();
+
         // Prompts Azure OpenAI with a request and synthesizes the response.
         async static Task AskOpenAI(string prompt)
         {
+            var speechConfig = SpeechConfig.FromSubscription(speechKey, speechRegion);
+            // The language of the voice that speaks.
+            speechConfig.SpeechSynthesisVoiceName = "en-US-JennyMultilingualNeural";
+            var audioOutputConfig = AudioConfig.FromDefaultSpeakerOutput();
+            using var speechSynthesizer = new SpeechSynthesizer(speechConfig, audioOutputConfig);
+            speechSynthesizer.Synthesizing += (sender, args) =>
+            {
+                lock (consoleLock)
+                {
+                    Console.ForegroundColor = ConsoleColor.Yellow;
+                    Console.Write($"[Audio]");
+                    Console.ResetColor();
+                }
+            };
+            
             // Ask Azure OpenAI
             OpenAIClient client = new(new Uri(openAIEndpoint), new AzureKeyCredential(openAIKey));
             var completionsOptions = new CompletionsOptions()
             {
                 Prompts = { prompt },
                 MaxTokens = 100,
+                
             };
-            Response<Completions> completionsResponse = client.GetCompletions(engine, completionsOptions);
-            string text = completionsResponse.Value.Choices[0].Text.Trim();
-            Console.WriteLine($"Azure OpenAI response: {text}");
-     
-            var speechConfig = SpeechConfig.FromSubscription(speechKey, speechRegion);
-            // The language of the voice that speaks.
-            speechConfig.SpeechSynthesisVoiceName = "en-US-JennyMultilingualNeural"; 
-            var audioOutputConfig = AudioConfig.FromDefaultSpeakerOutput();
-    
-            using (var speechSynthesizer = new SpeechSynthesizer(speechConfig, audioOutputConfig))
+            var responseStream = await client.GetCompletionsStreamingAsync(engine, completionsOptions);
+            using var streamingCompletions = responseStream.Value;
+            StringBuilder gptBuffer = new();
+            await foreach (var choice in streamingCompletions.GetChoicesStreaming())
             {
-                var speechSynthesisResult = await speechSynthesizer.SpeakTextAsync(text).ConfigureAwait(true);
-    
-                if (speechSynthesisResult.Reason == ResultReason.SynthesizingAudioCompleted)
+                await foreach (var message in choice.GetTextStreaming())
                 {
-                    Console.WriteLine($"Speech synthesized to speaker for text: [{text}]");
-                }
-                else if (speechSynthesisResult.Reason == ResultReason.Canceled)
-                {
-                    var cancellationDetails = SpeechSynthesisCancellationDetails.FromResult(speechSynthesisResult);
-                    Console.WriteLine($"Speech synthesis canceled: {cancellationDetails.Reason}");
-    
-                    if (cancellationDetails.Reason == CancellationReason.Error)
+                    if (string.IsNullOrEmpty(message))
+                    {
+                        continue;
+                    }
+        
+                    lock (consoleLock)
                     {
-                        Console.WriteLine($"Error details: {cancellationDetails.ErrorDetails}");
+                        Console.ForegroundColor = ConsoleColor.DarkBlue;
+                        Console.Write($"{message}");
+                        Console.ResetColor();
+                    }
+        
+                    gptBuffer.Append(message);
+                    
+                    if (sentenceSaperators.Any(message.Contains))
+                    {
+                        var sentence = gptBuffer.ToString().Trim();
+                        if (!string.IsNullOrEmpty(sentence))
+                        {
+                            await speechSynthesizer.SpeakTextAsync(sentence).ConfigureAwait(true);
+                            gptBuffer.Clear();
+                        }
                     }
                 }
             }
@@ -164,7 +189,7 @@ Follow these steps to create a new console application.
             }
         }
     }
-    ```
+```
 
 1. To increase or decrease the number of tokens returned by Azure OpenAI, change the `MaxTokens` property in the `CompletionsOptions` class instance. For more information tokens and cost implications, see [Azure OpenAI tokens](/azure/ai-services/openai/overview#tokens) and [Azure OpenAI pricing](https://azure.microsoft.com/pricing/details/cognitive-services/openai-service/).
 

articles/ai-services/speech-service/includes/quickstarts/openai-speech/python.md

@@ -48,7 +48,7 @@ Follow these steps to create a new console application.
 
 1. Copy the following code into `openai-speech.py`: 
 
-    ```Python
+```Python
     import os
     import azure.cognitiveservices.speech as speechsdk
     import openai
@@ -75,26 +75,30 @@ Follow these steps to create a new console application.
     # The language of the voice that responds on behalf of Azure OpenAI.
     speech_config.speech_synthesis_voice_name='en-US-JennyMultilingualNeural'
     speech_synthesizer = speechsdk.SpeechSynthesizer(speech_config=speech_config, audio_config=audio_output_config)
+
+    # tts sentence end mark
+    tts_sentence_end = [ ".", "!", "?", ";", "。", "！", "？", "；", "\n" ]
     
     # Prompts Azure OpenAI with a request and synthesizes the response.
     def ask_openai(prompt):
+        # Ask Azure OpenAI in streaming way
+        response = openai.Completion.create(engine=deployment_id, prompt=prompt, max_tokens=200, stream=True)
+        collected_messages = []
+        last_tts_request = None
     
-        # Ask Azure OpenAI
-        response = openai.Completion.create(engine=deployment_id, prompt=prompt, max_tokens=100)
-        text = response['choices'][0]['text'].replace('\n', ' ').replace(' .', '.').strip()
-        print('Azure OpenAI response:' + text)
-        
-        # Azure text to speech output
-        speech_synthesis_result = speech_synthesizer.speak_text_async(text).get()
-    
-        # Check result
-        if speech_synthesis_result.reason == speechsdk.ResultReason.SynthesizingAudioCompleted:
-            print("Speech synthesized to speaker for text [{}]".format(text))
-        elif speech_synthesis_result.reason == speechsdk.ResultReason.Canceled:
-            cancellation_details = speech_synthesis_result.cancellation_details
-            print("Speech synthesis canceled: {}".format(cancellation_details.reason))
-            if cancellation_details.reason == speechsdk.CancellationReason.Error:
-                print("Error details: {}".format(cancellation_details.error_details))
+        # iterate through the stream response stream
+        for chunk in response:
+            if len(chunk['choices']) > 0:
+                chunk_message = chunk['choices'][0]['text']  # extract the message
+                collected_messages.append(chunk_message)  # save the message
+                if chunk_message in tts_sentence_end: # sentence end found
+                    text = ''.join(collected_messages).strip() # join the recieved message together to build a sentence
+                    if text != '': # if sentence only have \n or space, we could skip
+                        print(f"Speech synthesized to speaker for: {text}")
+                        last_tts_request = speech_synthesizer.speak_text_async(text)
+                        collected_messages.clear()
+        if last_tts_request:
+            last_tts_request.get()
     
     # Continuously listens for speech input to recognize and send as text to Azure OpenAI
     def chat_with_open_ai():
@@ -128,7 +132,8 @@ Follow these steps to create a new console application.
         chat_with_open_ai()
     except Exception as err:
         print("Encountered exception. {}".format(err))
-    ```
+```
+
 1. To increase or decrease the number of tokens returned by Azure OpenAI, change the `max_tokens` parameter. For more information tokens and cost implications, see [Azure OpenAI tokens](/azure/ai-services/openai/overview#tokens) and [Azure OpenAI pricing](https://azure.microsoft.com/pricing/details/cognitive-services/openai-service/).
 
 Run your new console application to start speech recognition from a microphone:

articles/azure-monitor/logs/media/queries/query-start.png

@@ -13,69 +13,39 @@ ms.date: 06/22/2022
 # Query packs in Azure Monitor Logs
 Query packs act as containers for log queries in Azure Monitor. They let you save log queries and share them across workspaces and other contexts in Log Analytics.
 
-## View query packs
-You can view and manage query packs in the Azure portal from the **Log Analytics query packs** menu. Select a query pack to view and edit its permissions. This article describes how to create a query pack by using the API.
-
-[![Screenshot that shows query packs.](media/query-packs/view-query-pack.png)](media/query-packs/view-query-pack.png#lightbox)
-
 ## Permissions
-You can set the permissions on a query pack when you view it in the Azure portal. Users require the following permissions to use query packs:
+You can set the permissions on a query pack when you view it in the Azure portal. You need the following permissions to use query packs:
 
 - **Reader**: Users can see and run all queries in the query pack.
 - **Contributor**: Users can modify existing queries and add new queries to the query pack.
 
   > [!IMPORTANT]
   > When a user needs to modify or add queries, always grant the user the Contributor permission on the `DefaultQueryPack`. Otherwise, the user won't be able to save any queries to the subscription, including in other query packs.
 
+## View query packs
+You can view and manage query packs in the Azure portal from the **Log Analytics query packs** menu. Select a query pack to view and edit its permissions. This article describes how to create a query pack by using the API.
+
+[![Screenshot that shows query packs.](media/query-packs/view-query-pack.png)](media/query-packs/view-query-pack.png#lightbox)
+
 ## Default query pack
-A query pack, called `DefaultQueryPack`, is automatically created in each subscription in a resource group called `LogAnalyticsDefaultResources` when the first query is saved. You can create queries in this query pack or create other query packs depending on your requirements.
+Azure Monitor automatically creates a query pack called `DefaultQueryPack` in each subscription in a resource group called `LogAnalyticsDefaultResources` when you save your first query. You can save queries to this query pack or create other query packs depending on your requirements.
 
 ## Use multiple query packs
-The single default query pack will be sufficient for most users to save and reuse queries. But there are reasons that you might want to create multiple query packs for users in your organization. For example, you might want to load different sets of queries in different Log Analytics sessions and provide different permissions for different collections of queries.
 
-When you create a new query pack by using the API, you can add tags that classify queries according to your business requirements. For example, you could tag a query pack to relate it to a particular department in your organization or to severity of issues that the included queries are meant to address. By using tags, you can create different sets of queries intended for different sets of users and different situations.
+The default query pack is sufficient for most users to save and reuse queries. You might want to create multiple query packs for users in your organization if, for example, you want to load different sets of queries in different Log Analytics sessions and provide different permissions for different collections of queries.
 
-## Query pack definition
-Each query pack is defined in a JSON file that includes the definition for one or more queries. Each query is represented by a block.
+When you [create a new query pack](#create-a-query-pack), you can add tags that classify queries based on your business needs. For example, you could tag a query pack to relate it to a particular department in your organization or to severity of issues that the included queries are meant to address. By using tags, you can create different sets of queries intended for different sets of users and different situations.
 
-```json
-{
-    "properties":
-       {
-        "displayName": "Query name that will be displayed in the UI",
-        "description": "Query description that will be displayed in the UI",
-        "body": "<<query text, standard KQL code>>",
-        "related": {
-            "categories": [
-                "workloads"
-            ],
-            "resourceTypes": [
-                "microsoft.insights/components"
-            ],
-            "solutions": [
-                "logmanagement"
-            ]
-        },
-        "tags": {
-            "Tag1": [
-                "Value1",
-                "Value2"
-            ]
-        },
-   }
-}
-```
+To add query packs to your Log Analytics workspace: 
 
-## Query properties
-Each query in the query pack has the following properties:
+1. Open Log Analytics and select **Queries** in the upper-right corner.
+1. In the upper-left corner on the **Queries** dialog, next to **Query packs**, click **0 selected**.
+1. Select the query packs that you want to add to the workspace.
 
-| Property | Description |
-|:---|:---|
-| displayName | Display name listed in Log Analytics for each query. |
-| description | Description of the query displayed in Log Analytics for each query. |
-| body        | Query written in Kusto Query Language. |
-| related     | Related categories, resource types, and solutions for the query. Used for grouping and filtering in Log Analytics by the user to help locate their query. Each query can have up to 10 of each type. Retrieve allowed values from https://api.loganalytics.io/v1/metadata?select=resourceTypes, solutions, and categories. |
-| tags        | Other tags used by the user for sorting and filtering in Log Analytics. Each tag will be added to Category, Resource Type, and Solution when you [group and filter queries](queries.md#find-and-filter-queries). |
+:::image type="content" source="media/query-packs/log-analytics-add-query-pack.png" alt-text="Screenshot that shows the Select query packs page in Log Analytics, where you can add query packs to a Log Analytics workspace." lightbox="media/query-packs/log-analytics-add-query-pack.png":::
+
+> [!IMPORTANT]
+> You can add up to five query packs to a Log Analytics workspace.
 
 ## Create a query pack
 You can create a query pack by using the REST API or from the **Log Analytics query packs** pane in the Azure portal. To open the **Log Analytics query packs** pane in the portal, select **All services** > **Other**.
@@ -127,6 +97,16 @@ The payload of the request is the JSON that defines one or more queries and the
 }
 ```
 
+Each query in the query pack has the following properties:
+
+| Property | Description |
+|:---|:---|
+| `displayName` | Display name listed in Log Analytics for each query. |
+| `description` | Description of the query displayed in Log Analytics for each query. |
+| `body`        | Query written in Kusto Query Language. |
+| `related`    | Related categories, resource types, and solutions for the query. Used for grouping and filtering in Log Analytics by the user to help locate their query. Each query can have up to 10 of each type. Retrieve allowed values from https://api.loganalytics.io/v1/metadata?select=resourceTypes, solutions, and categories. |
+| `tags`        | Other tags used by the user for sorting and filtering in Log Analytics. Each tag will be added to Category, Resource Type, and Solution when you [group and filter queries](queries.md#find-and-filter-queries). |
+
 ### Create a request
 Use the following request to create a new query pack by using the REST API. The request should use bearer token authorization. The content type should be `application/json`.
 

articles/azure-monitor/logs/media/query-packs/log-analytics-add-query-pack.png

@@ -51,18 +51,72 @@ With the new geo-replication feature, Contoso can now establish a replica in Can
 ![Diagram of using one Azure SignalR instance with replica to handle traffic from two countries.](./media/howto-enable-geo-replication/signalr-replica.png "Replica Example")
 
 ## Create a SignalR replica
-
+# [Portal](#tab/Portal)
 To create a replica, Navigate to the SignalR **Replicas** blade on the Azure portal and click **Add** to create a replica. It will be automatically enabled upon creation.
 
 ![Screenshot of creating replica for Azure SignalR on Portal.](./media/howto-enable-geo-replication/signalr-replica-create.png "Replica create")
 
-> [!NOTE]
-> * Geo-replication is a feature available in premium tier.
-> * A replica is considered a separate resource when it comes to billing. See [Pricing and resource unit](#pricing-and-resource-unit) for more details. 
-
 After creation, you would be able to view/edit your replica on the portal by clicking the replica name.
 
 ![Screenshot of overview blade of Azure SignalR replica resource. ](./media/howto-enable-geo-replication/signalr-replica-overview.png "Replica Overview")
+# [Bicep](#tab/Bicep)
+
+Use Visual Studio Code or your favorite editor to create a file with the following content and name it main.bicep:
+
+```bicep
+@description('The name for your SignalR service')
+param primaryName string = 'contoso'
+
+@description('The region in which to create your SignalR service')
+param primaryLocation string = 'eastus'
+
+@description('Unit count of your SignalR service')
+param primaryCapacity int = 1
+
+resource primary 'Microsoft.SignalRService/signalr@2023-08-01-preview' = {
+  name: primaryName
+  location: primaryLocation
+  sku: {
+    capacity: primaryCapacity
+    name: 'Premium_P1'
+  }
+  properties: {
+  }
+}
+
+@description('The name for your SignalR replica')
+param replicaName string = 'contoso-westus'
+
+@description('The region in which to create the SignalR replica')
+param replicaLocation string = 'westus'
+
+@description('Unit count of the SignalR replica')
+param replicaCapacity int = 1
+
+@description('Whether to enable region endpoint for the replica')
+param regionEndpointEnabled string = 'Enabled'
+
+resource replica 'Microsoft.SignalRService/signalr/replicas@2023-08-01-preview' = {
+  parent: primary
+  name: replicaName
+  location: replicaLocation
+  sku: {
+    capacity: replicaCapacity
+    name: 'Premium_P1'
+  }
+  properties: {
+    regionEndpointEnabled: regionEndpointEnabled
+  }
+}
+```
+
+Deploy the Bicep file using Azure CLI 
+   ```azurecli
+   az group create --name MyResourceGroup --location eastus
+   az deployment group create --resource-group MyResourceGroup --template-file main.bicep
+   ```
+
+----
 
 ## Pricing and resource unit
 Each replica has its **own** `unit` and `autoscale settings`.

articles/azure-monitor/logs/query-packs.md

@@ -507,6 +507,10 @@ items:
       displayName: active directory
     - name: Microsoft Access
       href: connector-microsoft-access.md
+    - name: Microsoft Fabric Lakehouse Files
+      href: connector-microsoft-fabric-lakehouse-files.md
+    - name: Microsoft Fabric Lakehouse Table
+      href: connector-microsoft-fabric-lakehouse-table.md
     - name: MongoDB
       href: connector-mongodb.md
       items: