Merge pull request #260696 from MicrosoftDocs/main

12/8 11:00 AM Publish

Author: Saisang

.openpublishing.redirection.json

@@ -23447,6 +23447,11 @@
             "redirect_url": "/azure/lighthouse/concepts/architecture",
             "redirect_document_id": true
         },
+        {
+            "source_path_from_root": "/articles/lighthouse/how-to/partner-earned-credit.md",
+            "redirect_url": "/azure/cost-management-billing/manage/link-partner-id",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/service-fabric-mesh/index.yml",
             "redirect_url": "/previous-versions/azure/service-fabric-mesh/service-fabric-mesh-overview",

articles/ai-studio/concepts/evaluation-metrics-built-in.md

@@ -263,7 +263,7 @@ You will be given a question, chatbot's response to the question, a chat history
 The chatbot must base its response exclusively on factual information extracted from the retrieved documents, utilizing paraphrasing, summarization, or inference techniques. When the chatbot responds to information that is not mentioned in or cannot be inferred from the retrieved documents, we refer to it as a grounded issue. 
 
  
-To rate the groundness of chat response, follow the below steps: 
+To rate the groundedness of chat response, follow the below steps: 
 
 1. Review the chat history to understand better about the question and chat response 
 
@@ -431,4 +431,4 @@ Think through step by step:
 
 - [Evaluate your generative AI apps via the playground](../how-to/evaluate-prompts-playground.md)
 - [Evaluate your generative AI apps with the Azure AI Studio or SDK](../how-to/evaluate-generative-ai-app.md)
-- [View the evaluation results](../how-to/evaluate-flow-results.md)
+- [View the evaluation results](../how-to/evaluate-flow-results.md)

articles/ai-studio/how-to/create-manage-compute.md

@@ -56,7 +56,7 @@ To create a compute instance in Azure AI Studio:
     :::image type="content" source="../media/compute/compute-scheduling.png" alt-text="Screenshot of the option to enable idle shutdown and create a schedule." lightbox="../media/compute/compute-scheduling.png":::
 
     > [!IMPORTANT]
-    > The compute can't be idle if you have [prompt flow runtime](./create-manage-runtime.md) in **Running** status on the compute. You need to delete any active runtime before the compute instance can be eligible for idle shutdown.
+    > The compute can't be idle if you have [prompt flow runtime](./create-manage-runtime.md) in **Running** status on the compute. You need to delete any active runtime before the compute instance can be eligible for idle shutdown. You also can't have any active [VS Code (Web)](./vscode-web.md) sessions hosted on the compute instance.
 
 1. You can update the schedule days and times to meet your needs. You can also add additional schedules. For example, you can create a schedule to start at 9 AM and stop at 6 PM from Monday-Thursday, and a second schedule to start at 9 AM and stop at 4 PM for Friday. You can create a total of four schedules per compute instance.
 
@@ -83,7 +83,7 @@ Note that disabling SSH prevents SSH access from the public internet. But when a
 To avoid getting charged for a compute instance that is switched on but inactive, you can configure when to shut down your compute instance due to inactivity. 
 
 > [!IMPORTANT]
-> The compute can't be idle if you have [prompt flow runtime](./create-manage-runtime.md) in **Running** status on the compute. You need to delete any active runtime before the compute instance can be eligible for idle shutdown.
+> The compute can't be idle if you have [prompt flow runtime](./create-manage-runtime.md) in **Running** status on the compute. You need to delete any active runtime before the compute instance can be eligible for idle shutdown. You also can't have any active [VS Code (Web)](./vscode-web.md) sessions hosted on the compute instance.
 
 The setting can be configured during compute instance creation or for existing compute instances.
 

articles/azure-monitor/agents/azure-monitor-agent-extension-versions.md

@@ -20,6 +20,7 @@ We strongly recommended to always update to the latest version, or opt in to the
 ## Version details
 | Release Date | Release notes | Windows | Linux |
 |:---|:---|:---|:---|
+| December 2023 | **Linux**<ul><li>Support for TLS V1.3</li><li>Support for nopri in Syslog</li><li>Ability to set disk quota from DCR Agent Settings</li><li>Add ARM64 Ubuntu 22 support</li><li>**Fixes**<ul><li>Parse syslog Palo Alto CEF with multiple space characters following the hostname</li><li>Fix AMA crash in RHEL 7.2</li><li>Remove dependency on "which" command</li><li>Fix port conflicts due to AMA using 13000 </li><li>Reliability and Performance improvements</li></ul></li></ul>|  | 1.29.4|
 | October 2023| **Windows** <ul><li>Minimize CPU spikes when resetting an Event Log subscription</li><li>Enable multiple IIS subscriptions to use same filter</li><li>Cleanup files and folders for inactive tenants in multi-tenant mode</li><li>AMA installer will not install unnecessary certs</li><li>AMA emits Telemetry table locally</li><li>Update Metric Extension to v2.2023.721.1630</li><li>Update AzureSecurityPack to v4.29.0.4</li><li>Update AzureWatson to v1.0.99</li></ul>**Linux**<ul><li> Add support for Process metrics counters for Log Analytics upload and Azure Monitor Metrics</li><li>Use rsyslog omfwd TCP for improved syslog reliability</li><li>Support Palo Alto CEF logs where hostname is followed by 2 spaces</li><li>Bug and reliability improvements</li></ul> |1.21.0|1.28.11|
 | September 2023| **Windows** <ul><li>Fix issue with high CPU usage due to excessive Windows Event Logs subscription reset</li><li>Reduce fluentbit resource usage by limiting tracked files older than 3 days and limiting logging to errors only</li><li>Fix race-condition where resource_id is unavailable when agent is restarted</li><li>Fix race-condition when vm-extension provision agent (aka GuestAgent) is issuing a disable-vm-extension command to AMA.</li><li>Update MetricExtension version to 2.2023.721.1630</li><li>Update Troubleshooter to v1.5.14 </li></ul>|1.20.0| None |
 | August 2023| **Windows** <ul><li>AMA: Allow prefixes in the tag names to handle regression</li><li>Updating package version for AzSecPack 4.28 release</li></ul>**Linux**<ul><li> Comming soon</li></ui>|1.19.0| Comming Soon |

articles/azure-portal/azure-portal-supported-browsers-devices.md

@@ -2,13 +2,13 @@
 title: Supported browsers and devices for Azure portal
 description: You can use the Azure portal on all modern devices and with the latest browser versions.
 ms.topic: conceptual
-ms.date: 09/12/2022
+ms.date: 12/07/2023
 ms.custom: accessibility
 ---
 
 # Supported devices
 
-The [Azure portal](https://portal.azure.com) is a web-based console and runs in the browser of all modern desktops and tablet devices. To use the portal, you must have JavaScript enabled on your browser. We recommend not using ad blockers in your browser because they may cause issues with some portal features.
+The [Azure portal](https://portal.azure.com) is a web-based console and runs in the browser of all modern desktops and tablet devices. To use the portal, you must have JavaScript enabled on your browser. We recommend not using ad blockers in your browser, because they may cause issues with some portal features.
 
 ## Recommended browsers
 
@@ -21,4 +21,4 @@ We recommend using the most up-to-date browser that's compatible with your opera
 
 ## Mobile app
 
-To manage Azure resources from a mobile device, try the [Azure mobile app](https://azure.microsoft.com/features/azure-portal/mobile-app/). It's available for iOS and Android.
+To manage Azure resources from a mobile device, try the [Azure mobile app](mobile-app/overview.md). It's available for iOS and Android.

articles/communication-services/concepts/interop/guest/capabilities.md

@@ -25,7 +25,7 @@ In this article, you will learn which capabilities are supported for Teams exter
 |                   | Prevent joining locked meeting                                                                                      | ✔️        |
 |                   | Honor assigned Teams meeting role                                                                                   |   ✔️      |
 | Chat              | Send and receive chat messages                                                                                      | ✔️ |
-|                   | [Receive inline images](../../../tutorials/chat-interop/meeting-interop-features-inline-image.md)                                                                    | ✔️** |
+|                   | [Receive inline images](../../../tutorials/chat-interop/meeting-interop-features-inline-image.md)                                                                    | ✔️ |
 |                   | Send inline images                                                                                                        | ❌ |
 |                   | [Receive file attachments](../../../tutorials/chat-interop/meeting-interop-features-file-attachment.md)                                                                                                           | ✔️** |
 |                   | Send file attachments                                                                                                        | ❌ |
@@ -172,7 +172,7 @@ When Teams external users leave the meeting, or the meeting ends, they can no lo
 
 *Azure Communication Services provides developers tools to integrate Microsoft Teams Data Loss Prevention that is compatible with Microsoft Teams. For more information, go to [how to implement Data Loss Prevention (DLP)](../../../how-tos/chat-sdk/data-loss-prevention.md)
 
-**Inline image and file attachment support are currently in public preview and are available in the Chat SDK for JavaScript only. Preview APIs and SDKs are provided without a service-level agreement. We recommend that you don't use them for production workloads. Some features might not be supported, or they might have constrained capabilities. For more information, review [Supplemental Terms of Use for Microsoft Azure Previews.](https://azure.microsoft.com/support/legal/preview-supplemental-terms/)
+**File attachment support is currently in public preview and is available in the Chat SDK for JavaScript only. Preview APIs and SDKs are provided without a service-level agreement. We recommend that you don't use them for production workloads. Some features might not be supported, or they might have constrained capabilities. For more information, review [Supplemental Terms of Use for Microsoft Azure Previews.](https://azure.microsoft.com/support/legal/preview-supplemental-terms/)
 
 ## Server capabilities
 

articles/communication-services/tutorials/chat-interop/includes/meeting-interop-features-file-attachment-javascript.md

@@ -17,7 +17,7 @@ Find the finalized code of this tutorial on [GitHub](https://github.com/Azure-Sa
 * You've gone through the quickstart - [Join your chat app to a Teams meeting](../../../quickstarts/chat/meeting-interop.md). 
 * Create an Azure Communication Services resource. For details, see [Create an Azure Communication Services resource](../../../quickstarts/create-communication-resource.md). You need to **record your connection string** for this tutorial.
 * You've set up a Teams meeting using your business account and have the meeting URL ready.
-* You're using the Chat SDK for JavaScript (@azure/communication-chat) 1.3.2-beta.2 or the latest. See [here](https://www.npmjs.com/package/@azure/communication-chat).
+* You're using the Chat SDK for JavaScript (@azure/communication-chat) 1.5.0-beta.1 or the latest. See [here](https://www.npmjs.com/package/@azure/communication-chat).
 
 ## Goal
 
@@ -26,7 +26,7 @@ Find the finalized code of this tutorial on [GitHub](https://github.com/Azure-Sa
 
 ## Handle file attachments
 
-The Chat SDK for JavaScript would return `AttachmentType` of `file` for regular files and `teamsImage` for image attachments.
+The Chat SDK for JavaScript returns a `ChatAttachmentType` of `file` for regular file attachments and `image` for message-inlined images.
 
 ```js
 export interface ChatMessageReceivedEvent extends BaseChatMessageEvent {
@@ -48,39 +48,34 @@ export interface ChatAttachment {
   id: string;
   /** The type of attachment. */
   attachmentType: AttachmentType;
-  /** The type of content of the attachment, if available */
-  contentType?: string;
   /** The name of the attachment content. */
   name?: string;
   /** The URL that is used to provide original size of the inline images */
-  url: string;
+  url?: string;
   /** The URL that provides the preview of attachment */
   previewUrl?: string;
 }
 
 /** Type of Supported Attachments. */
-export type AttachmentType = "teamsInlineImage" | "teamsImage" | "file";
+export type ChatAttachmentType = "image" | "file" | "unknown";
 ```
 
 As an example, the following JSON is an example of what `ChatAttachment` might look like for an image attachment and a file attachment:
 
-```js
+```json
 "attachments": [
     {
         "id": "08a182fe-0b29-443e-8d7f-8896bc1908a2",
         "attachmentType": "file",
-        "contentType": "pdf",
         "name": "business report.pdf",
-        "url": "",
         "previewUrl": "https://contoso.sharepoint.com/:u:/g/user/h8jTwB0Zl1AY"
     },
     {
         "id": "9d89acb2-c4e4-4cab-b94a-7c12a61afe30",
-        "attachmentType": "teamsImage",
-        "contentType": "png",
+        "attachmentType": "image", 
         "name": "Screenshot.png",
-        "url": "https://contoso.communication.azure.com/chat/threads/19:[email protected]/messages/123/teamsInterop/images/9d89acb2-c4e4-4cab-b94a-7c12a61afe30/views/original?api-version=2023-07-01-preview",
-        "previewUrl": "https://contoso.communication.azure.com/chat/threads/19:[email protected]/messages/123/teamsInterop/images/9d89acb2-c4e4-4cab-b94a-7c12a61afe30/views/small?api-version=2023-07-01-preview"
+        "url": "https://contoso.communication.azure.com/chat/threads/19:[email protected]/messages/123/images/9d89acb2-c4e4-4cab-b94a-7c12a61afe30/views/original?api-version=2023-11-15-preview",
+        "previewUrl": "https://contoso.communication.azure.com/chat/threads/19:[email protected]/messages/123/images/9d89acb2-c4e4-4cab-b94a-7c12a61afe30/views/small?api-version=2023-11-15-preview"
       }
 ]
 ```
@@ -115,10 +110,12 @@ async function renderReceivedMessage(event) {
 }
 
 function renderFileAttachments(attachment) {
+    var re = /(?:\.([^.]+))?$/;
+    var fileExtension = re.exec(attachment.name)[1];  
     return '<div class="attachment-container">' +
-        '<p class="attachment-type">' + attachment.contentType + '</p>' +
         '<img class="attachment-icon" alt="attachment file icon" />' +
         '<div>' +
+        '<p class="attachment-type">' + fileExtension + '</p>' +
         '<p>' + attachment.name + '</p>' +
         '<a href=' + attachment.previewUrl + ' target="_blank" rel="noreferrer">Open</a>' +
         '</div>' +
@@ -227,7 +224,7 @@ Then you should see the new message being rendered along with file attachments:
 
 ## Handle image attachments
 
-In addition to regular files, image attachment needs to be treated differently. As we wrote in the beginning, the image attachment has `attachmentType` of `teamsImage`, which requires the communication token to retrieve the preview image and full scale image.
+Image attachments need to be treated differently to standard `file` attachments. Image attachment have the `attachmentType` of `image`, which requires the communication token to retrieve either the preview or full-size images.
 
 Before we go any further, make sure you have gone through the tutorial that demonstrates [how you can enable inline image support in your chat app](../meeting-interop-features-inline-image.md). To summary, fetching images require a communication token in the request header. Upon getting the image blob, we need to create an `ObjectUrl` that points to this blob. Then we inject this URL to `src` attribute of each inline image.
 
@@ -242,7 +239,7 @@ async function renderReceivedMessage(event) {
 
     // Inject image tag for all image attachments
     var imageAttachmentHtml = event.attachments
-        .filter(attachment => attachment.attachmentType === "teamsImage")
+        .filter(attachment => attachment.attachmentType === "image" && !messages.includes(attachment.id))
         .map(attachment => renderImageAttachments(attachment))
         .join('');
     messagesContainer.innerHTML += imageAttachmentHtml;
@@ -256,8 +253,7 @@ async function renderReceivedMessage(event) {
 
     // filter out inline images from attchments
     const imageAttachments = event.attachments.filter((attachment) =>
-        attachment.attachmentType === "teamsInlineImage" ||
-        attachment.attachmentType === "teamsImage");
+        attachment.attachmentType === "image" && messages.includes(attachment.id));
 
     // fetch and render preview images
     fetchPreviewImages(imageAttachments);