Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into sla

Author: dlepow

articles/app-service/configure-ssl-certificate.md

@@ -82,12 +82,13 @@ The free certificate comes with the following limitations:
 
 ### [Apex domain](#tab/apex)
 - Must have an A record pointing to your web app's IP address.
-- Isn't supported on apps that aren't publicly accessible.
+- Must be on apps that are publicly accessible.
 - Isn't supported with root domains that are integrated with Traffic Manager.
 - Must meet all the above for successful certificate issuances and renewals.
 
 ### [Subdomain](#tab/subdomain)
 - Must have CNAME mapped _directly_ to `<app-name>.azurewebsites.net` or [trafficmanager.net](configure-domain-traffic-manager.md#enable-custom-domain). Mapping to an intermediate CNAME value blocks certificate issuance and renewal.
+- Must be on apps that are publicly accessible.
 - Must meet all the above for successful certificate issuance and renewals.
 
 ---

articles/azure-monitor/azure-monitor-operations-manager.md

@@ -31,7 +31,7 @@ The following table describes the different features and strategies that are ava
 |:---|:---|
 | Dual-homed agents | SCOM uses the Microsoft Management Agent (MMA), which is the same as [Log Analytics agent](agents/log-analytics-agent.md) used by Azure Monitor. You can configure this agent to have a single machine connect to both SCOM and Azure Monitor simultaneously. This configuration does require that your Azure VMs have a connection to your on-premises management servers.<br><br>The [Log Analytics agent](agents/log-analytics-agent.md) has been replaced with the [Azure Monitor agent](agents/agents-overview.md), which provides significant advantages including simpler management and better control over data collection. The two agents can coexist on the same machine allowing you to connect to both Azure Monitor and SCOM. This configuration is a better option than dual-homing the legacy agent because of the significant [advantages of the Azure Monitor agent](agents/agents-overview.md#benefits). |
 | Connected management group | [Connect your SCOM management group to Azure Monitor](agents/om-agents.md) to forward data collected from your SCOM agents to Azure Monitor. This is similar to using dual-homed agents, but doesn't require each agent to be configured to connect to Azure Monitor. This strategy requires the legacy agent, so you can't specify monitoring with data collection rules. You also can't use VM insights unless you connect each VM directly to Azure Monitor. |
-| SCOM Managed instance | [SCOM managed instance (preview)](vm/scom-managed-instance-overview.md) is a full implementation of SCOM in Azure allowing you to continue running the same management packs that you run in your on-premises SCOM environment. You can continue to use the same Operations console for analyzing your health and alerts and can also view alerts in Azure Monitor and analyze SCOM data in Grafana.<br><br>SCOM MI is similar to maintaining your existing SCOM environment and dual-homing agents, although you can consolidate your monitoring configuration in Azure and retire your on-premises components such as database and management servers. Agents from Azure VMs can connect to the SCOM managed instance in Azure rather than connecting to management servers in your own data center. |
+| SCOM Managed instance | [SCOM managed instance](vm/scom-managed-instance-overview.md) is a full implementation of SCOM in Azure allowing you to continue running the same management packs that you run in your on-premises SCOM environment. You can continue to use the same Operations console for analyzing your health and alerts and can also view alerts in Azure Monitor and analyze SCOM data in Grafana.<br><br>SCOM MI is similar to maintaining your existing SCOM environment and dual-homing agents, although you can consolidate your monitoring configuration in Azure and retire your on-premises components such as database and management servers. Agents from Azure VMs can connect to the SCOM managed instance in Azure rather than connecting to management servers in your own data center. |
 |  Azure management pack | The [Azure management pack](https://www.microsoft.com/download/details.aspx?id=50013) allows Operations Manager to discover Azure resources and monitor their health based on a particular set of monitoring scenarios. This management pack does require you to perform extra configuration for each resource in Azure. It may be helpful though to provide some visibility of your Azure resources in the Operations Console until you evolve your business processes to focus on Azure Monitor. |
 
 ## Monitor business applications

articles/azure-monitor/containers/media/prometheus-metrics-troubleshoot/throttling.png

@@ -12,15 +12,13 @@ Follow the steps in this article to determine the cause of Prometheus metrics no
 
 Replica pod scrapes metrics from `kube-state-metrics`, custom scrape targets in the `ama-metrics-prometheus-config` configmap and custom scrape targets defined in the [Custom Resources](prometheus-metrics-scrape-crd.md). DaemonSet pods scrape metrics from the following targets on their respective node: `kubelet`, `cAdvisor`, `node-exporter`, and custom scrape targets in the `ama-metrics-prometheus-config-node` configmap. The pod that you want to view the logs and the Prometheus UI for it depends on which scrape target you're investigating.
 
-## Troubleshoot using powershell script
+## Troubleshoot using PowerShell script
 
-If you encounter an error while you attempt to enable monitoring for your AKS cluster, please follow the instructions mentioned [here](https://github.com/Azure/prometheus-collector/tree/main/internal/scripts/troubleshoot) to run the troubleshooting script. This script is designed to do a basic diagnosis of for any configuration issues on your cluster and you can ch the generated files while creating a support request for faster resolution for your support case.
-
-## Missing metrics
+If you encounter an error while you attempt to enable monitoring for your AKS cluster, follow [these instructions](https://github.com/Azure/prometheus-collector/tree/main/internal/scripts/troubleshoot) to run the troubleshooting script. This script is designed to do a basic diagnosis for any configuration issues on your cluster and you can attach the generated files while creating a support request for faster resolution for your support case.
 
 ## Metrics Throttling
 
-In the Azure portal, navigate to your Azure Monitor Workspace. Go to `Metrics` and verify that the metrics `Active Time Series % Utilization` and `Events Per Minute Ingested % Utilization` are below 100%.
+In the Azure portal, navigate to your Azure Monitor Workspace. Go to `Metrics`, click on the `Add Metric` dropdown and then click on the `Add with builder` option to verify that the metrics `Active Time Series % Utilization` and `Events Per Minute Ingested % Utilization` are below 100%.
 
 :::image type="content" source="media/prometheus-metrics-troubleshoot/throttling.png" alt-text="Screenshot showing how to navigate to the throttling metrics." lightbox="media/prometheus-metrics-troubleshoot/throttling.png":::
 
@@ -192,7 +190,7 @@ Refer to [service quotas and limits](../service-limits.md#prometheus-metrics) fo
 
 ## Creation of Azure Monitor Workspace failed due to Azure Policy evaluation
 
-If creation of Azure Monitor Workspace fails with an error saying "*Resource 'resource-name-xyz' was disallowed by policy*", there might an Azure policy that is preventing the resource to be created. If there is a policy that enforces a naming convention for your Azure resources or resource groups, you will need to create an exemption for the naming convention for creation of an Azure Monitor Workspace.
+If creation of Azure Monitor Workspace fails with an error saying "*Resource 'resource-name-xyz' was disallowed by policy*", there might be an Azure policy that is preventing the resource to be created. If there is a policy that enforces a naming convention for your Azure resources or resource groups, you will need to create an exemption for the naming convention for creation of an Azure Monitor Workspace.
 
 When you create an Azure Monitor workspace, by default a data collection rule and a data collection endpoint in the form "*azure-monitor-workspace-name*" will automatically be created in a resource group in the form "*MA_azure-monitor-workspace-name_location_managed*". Currently there is no way to change the names of these resources, and you will need to set an exemption on the Azure Policy to exempt the above resources from policy evaluation. See [Azure Policy exemption structure](../../governance/policy/concepts/exemption-structure.md).
 

articles/azure-monitor/containers/prometheus-metrics-troubleshoot.md

@@ -12,13 +12,13 @@ Use the `CallComposite` and the `ChatComposite` in the Azure Communication Servi
 
 You can use the call composite in Communication Services to create these use cases:
 
-| Area                                                                                            | Use cases                                              |
-| ----------------------------------------------------------------------------------------------- | ------------------------------------------------------ |
-| Call types                                                                                      | Join a Microsoft Teams meeting                                     |
-|                                                                                                 | Join a Microsoft Teams meeting using Meeting ID and Passcode      |
-|                                                                                                 | Join a call by using a group ID                                  |
-|                                                                                                 | Join a call by using a room  ID                                  |
-|                                                                                                 | Make and Receive 1:1 Calls                      |
+| Area                                                                 | Use cases                                                       |
+| -------------------------------------------------------------------- | --------------------------------------------------------------- |
+| Call types                                                           | Join a Microsoft Teams meeting                                  |
+|                                                                      | Join a Microsoft Teams meeting using Meeting ID and Passcode    |
+|                                                                      | Join a call by using a group ID                                 |
+|                                                                      | Join a call by using a room  ID                                 |
+|                                                                      | Make and Receive 1:1 Calls                                      |
 | [Teams interoperability](../../teams-interop.md)                     | Join the call lobby                                             |
 |                                                                                                 | Display a transcription and recording alert banner               |
 |                                                                                                 | Admit/Reject lobby participants                                 |
@@ -41,6 +41,8 @@ You can use the call composite in Communication Services to create these use cas
 |                                                                                                 | End a call                                               |
 |                                                                                                 | Hold and resume a call after audio interruption                 |
 |                                                                                                 | CallKit and TelecomManager Support                 |
+| Customize the experience                                             | Button bar customization                                        |
+
 
 ### Teams interoperability
 
@@ -94,6 +96,37 @@ You can use the UI Library call composite for iOS and Android to create a custom
 | -------------------------------------------------------- | --------------------------------------------------------------- |
 | :::image type="content" source="../../media/mobile-ui/android-color.png" alt-text="Screenshot that shows Android theming for a caller experience."::: | :::image type="content" source="../../media/mobile-ui/ios-dark.png" alt-text="Screenshot that shows iOS theming for a caller experience.":::  |
 
+### Button bar customization
+
+The functionality allows developers to add new actions into the contextual menu or remove current buttons in the button bar, providing the flexibility to introduce custom actions and tailor the user interface according to specific application needs.
+
+- Add Custom Buttons: Developers can introduce new buttons into the contextual button bar to trigger custom actions.
+- Remove Existing Buttons: Unnecessary default buttons can be removed to streamline the interface: camera, microphone o audio selection.
+
+Consider the following constraints during the implementation of this feature:
+
+- Icons and Labels: Icons are added only for new actions. The button bar icons keep the predefined icon, labels should be concise to fit the menu dimension.
+- Accessibility Considerations: Developers should ensure that all custom buttons are accessible, including appropriate labeling for screen readers.
+
+|Remove buttons | Add custom actions|
+|-------------  | ------------------|
+| :::image type="content" source="media/ui-library-remove-button.png" alt-text="Screenshot that demonstrates the remove button on the bottom bar."::: |  :::image type="content" source="media/ui-library-add-action-button.png" alt-text="Screenshot that demonstrates add custom action into the contextual menu."::: |
+
+#### Use cases
+
+- Custom In-Call Actions: A business application can add a custom "Report Issue" button, allowing users to directly report technical issues during a call.
+- Branding and User Experience: An enterprise app can remove buttons that are irrelevant to its use case and add branded buttons that enhance the user experience.
+
+To ensure a consistent call experience, , we recommend that you integrate Fluent UI icons into your project; available at [Fluent UI GitHub repository](https://github.com/microsoft/fluentui-system-icons/). By doing so, your custom icons will match the design of the Call Composite, creating a cohesive and professional appearance.
+
+#### Best practices
+
+- Minimalism: Avoid overcrowding the contextual menu bar. Only add buttons that are essential for the user experience.
+- User Testing: Conduct user testing to ensure the customizations meets user needs and don't confuse or overwhelm them.
+- Add a Feedback Mechanism: If adding buttons for actions like "Report Issue," ensure there's a robust backend system to handle the feedback collected, you can reuse the [mechanism that UI Library provides by default](../../../tutorials/collecting-user-feedback/collecting-user-feedback.md).
+
+For more information, see [How to customize the button bar](../../../how-tos/ui-library-sdk/button-injection.md).
+
 ### Screen size
 
 You can adapt the Azure Communication Services call composite to adapt to screen sizes from 5 inches to tablet size. Use split mode and tablet mode in the call composite to get the dynamic participants' roster layout, provide clarity on the view, and focus on the conversation.

articles/communication-services/concepts/ui-library/includes/media/ui-library-add-action-button.png

@@ -0,0 +1,45 @@
+---
+title: Customize the actions from the button bar in the UI Library
+titleSuffix: An Azure Communication Services how-to guide
+description: Customize the actions from the button bar in the Azure Communication Services UI Library.
+author: garchiro7
+
+ms.author: jorgegarc
+ms.service: azure-communication-services
+ms.subservice: calling
+ms.topic: how-to 
+ms.date: 08/01/2024
+ms.custom: template-how-to
+zone_pivot_groups: acs-plat-ios-android
+
+#Customer intent: As a developer, I want to customize the button bar actions in the UI Library.
+---
+
+# Customize the button bar
+
+[!INCLUDE [Public Preview Notice](../../includes/public-preview-include.md)]
+
+To implement custom actions or modify the current button layout, you can interact with the Native UI Library's API. This API involves defining custom button configurations, specifying actions, and managing the button bar's current actions. The API provides methods for adding custom actions, and removing existing buttons, all of which are accessible via straightforward function calls.
+
+This functionality provides a high degree of customization, and ensures that the user interface remains cohesive and consistent with the application's overall design.
+
+## Prerequisites
+
+- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
+- A deployed Communication Services resource. [Create a Communication Services resource](../../quickstarts/create-communication-resource.md).
+- A user access token to enable the call client. [Get a user access token](../../quickstarts/access-tokens.md).
+- Optional: Completion of the [quickstart for getting started with the UI Library composites](../../quickstarts/ui-library/get-started-composites.md).
+
+## Set up the feature
+
+::: zone pivot="platform-android"
+[!INCLUDE [Customize the actions from the button bar in the Android UI Library](./includes/button-injection/android.md)]
+::: zone-end
+
+::: zone pivot="platform-ios"
+[!INCLUDE [DCustomize the actions from the button bar in the iOS UI Library](./includes/button-injection/ios.md)]
+::: zone-end
+
+## Next steps
+
+- [Learn more about the UI Library](../../concepts/ui-library/ui-library-overview.md)