Merge pull request #299316 from MicrosoftDocs/main

ttorble · web-flow · commit 205dc822f0c5 · 2025-05-05T12:09:21.000+01:00
Publish to live, Monday 4 AM PST, 5/5
diff --git a/articles/active-directory-b2c/service-limits.md b/articles/active-directory-b2c/service-limits.md
@@ -190,7 +190,7 @@ As a protection for our customers, Microsoft places some restrictions on telepho
 | 221 | Senegal | 10 | 30 |
 | 223 | Mali | 20 | 100 |
 | 224 | Guinea | 20 | 100 |
-| 225 |	Ivory Coast|	10	| 30 |
+| 225 |	Côte d’Ivoire |	10	| 30 |
 | 226 |  Burina Faso   | 10  |  30  |
 | 228 |  Togo  | 10  |  30  |
 | 233 |	Ghana|	10	| 30 |
@@ -219,7 +219,7 @@ As a protection for our customers, Microsoft places some restrictions on telepho
 | 60 | Malaysia | 50 | 200 |
 | 62 |  Indonesia | 50  |  200 |
 | 63 |  Philippines   | 50  |  200 |
-| 670 |	East Timor (Timor-Leste)  |	10	| 30 |
+| 670 |	Timor-Leste  |	10	| 30 |
 | 7 |  Russia | 100  |  1000 |
 | 84 |  Vietnam   | 150  |  500 |
 | 855 |  Cambodia  | 50  |  200 |
@@ -228,7 +228,7 @@ As a protection for our customers, Microsoft places some restrictions on telepho
 | 92 |  Pakistan| 100  |  1000 |
 | 93 |	Afghanistan  |	10	| 30 |
 | 94 |  Sri Lanka | 100  |  500 |
-| 95 |	Myanmar (Burma) | 10	| 30 |
+| 95 |	Myanmar | 10	| 30 |
 | 961 |	Lebanon  |	10	| 30 |
 | 967 |	Yemen	|10	| 30 |
 | 970 |  State of Palestine| 10  |  30  |
diff --git a/articles/communication-services/concepts/managed-apps.md b/articles/communication-services/concepts/managed-apps.md
@@ -0,0 +1,67 @@
+---
+title: Azure managed applications
+titleSuffix: An Azure Communication Services article
+description: This article describes how to offer your customers cloud solutions using Azure managed applications for Azure Communication Services.
+author: pgrandhi
+manager: rajasekaran2003
+services: azure-communication-services
+
+ms.author: pgrandhi
+ms.date: 04/09/2025
+ms.topic: conceptual
+ms.service: azure-communication-services
+---
+
+# Managed applications
+
+This article describes how you can use Azure managed applications to offer cloud solutions that are easy for customers to deploy and operate.
+
+Customers also control the permissions that enable full access to resources in the managed resource group. Customers can make sure that all end users are using approved versions, compliant with organizational standards. Your customers don't need to develop application-specific domain knowledge to manage these applications. Your customers automatically acquire application updates without the need to worry about troubleshooting and diagnose issues with the applications.
+
+Azure managed applications enable you to build and manage complete solutions in Azure. Managed applications enable you to offer cloud solutions that are easy for customers to deploy and operate.  
+
+You implement the infrastructure and can provide ongoing support. You determine if your managed application is public or private:
+
+- You can offer managed application to all customers by publishing in Azure Marketplace.
+- Or, you can make your managed application available only within your organization by publishing to an internal service catalog.
+
+A managed application is similar to a solution template in Azure Marketplace. The main difference is that if you publish a managed application, you specify the cost to your customers for ongoing support of the solution.
+
+Managed applications enable you to define terms for managing the application and all charges are handled through Azure billing. You can deploy managed applications via your subscriptions, but you don't need to maintain, update, or service them.
+
+:::image type="content" source="../../azure-resource-manager/managed-applications/media/overview/managed-apps-resource-group.png" alt-text="Diagram that shows the relationship between customer and publisher Azure subscriptions for a managed resource group.":::
+
+## How to implement
+
+To publish a managed application to your service catalog, you need to:
+
+1. Create an Azure ARM template that defines the Azure resources you want to deploy with the managed application. Every managed application includes a `mainTemplate.json` file.
+2. Define the nested ARM templates as needed in their own JSON files in a subfolder, to be included in the `mainTemplate.json` file.
+3. Create the portal experience to for the managed application. Use the `createUiDefinition.json` file to generate the portal user interface. Define the portal user interface elements for that customers see when deploying the managed application.
+4. Create a `.zip` package that contains the required JSON files. The `.zip` package file has a 120-MB limit for a service catalog's managed application definition.
+5. Publish the managed application definition so it's available in your service catalog.
+
+For more information, see [Advantages of managed applications](/azure/azure-resource-manager/managed-applications/overview#advantages-of-managed-applications).
+
+## Sample applications
+
+Azure Communication Services managed applications provide samples that showcase how you can use the Azure Resource Manager (ARM) templates. Use the ARM templates to implement infrastructure for specific Azure Communication Services scenarios.
+
+For example, you can:
+
+- Create an Azure Communication Services resource.
+- Create a storage queue.
+- Set up the storage queue as event subscription for your resource using managed identities.
+- Enable diagnostic settings for the resource for troubleshooting purposes. 
+- Access diagnostic logs and update any infrastructure as needed over time. 
+
+For more information about the sample applications, see GitHub Azure Samples [Managed Communication Services](https://github.com/Azure-Samples/communication-services-azure-managed-apps/blob/fca4bcad7516cf6c001c171272aceda4ed62c7a0/ManagedApplicationSamples/readme.md).
+
+## Next steps
+
+> [!div class="nextstepaction"]
+> [Create an Azure Communication Services managed application](https://github.com/Azure-Samples/communication-services-azure-managed-apps/blob/fca4bcad7516cf6c001c171272aceda4ed62c7a0/ManagedApplicationSamples/readme.md)
+
+## Related articles
+
+[Azure managed applications overview](/azure/azure-resource-manager/managed-applications/overview)
diff --git a/articles/communication-services/toc.yml b/articles/communication-services/toc.yml
@@ -18,6 +18,8 @@ items:
     href: quickstarts/create-communication-resource.md
 #  - name: Geolocation
 #    href: /rest/api/maps/geolocation
+  - name: Managed applications
+    href: concepts/managed-apps.md
   - name: SDKs and APIs
     href: concepts/sdk-options.md
   - name: Service limits
diff --git a/articles/defender-for-iot/organizations/cli-ot-sensor.md b/articles/defender-for-iot/organizations/cli-ot-sensor.md
@@ -19,6 +19,51 @@ While this article lists the command syntax for each user, we recommend using th
 
 For more information, see [Access the CLI](../references-work-with-defender-for-iot-cli-commands.md#access-the-cli) and [Privileged user access for OT monitoring](references-work-with-defender-for-iot-cli-commands.md#privileged-user-access-for-ot-monitoring).
 
+## List of available commands
+
+| Category| Command |
+|****|*****|
+| config | config |
+| system | backup </br>date</br>hostname</br>ntp</br>password</br>reboot</br>sanity</br>shell</br>shutdown</br>syslog</br>version|
+| network |  blink</br>capture-filter</br>list</br>ping</br>reconfigure</br>statistics</br>validate|
+
+### List commands in a category
+
+To list the commands in a category, type ```help```. For example:
+
+```bash
+shell> help
+config:
+network:
+system:
+
+shell> help system
+backup:
+date:
+ntp:
+```
+
+### Commands at the shell and category level
+
+You can type commands at the shell or category level.
+
+At the shell level type: \<category> \<command> \<parameter>.
+
+Alternatively, type the \<category> and press ENTER. The shell will change to the category name, then type \<command> \<parameter>. For example:
+
+```bash
+shell> system ntp enable 10.0.0.1
+Starting ntp-enable 10.0.0.1
+.....
+Finished ntp-enable
+
+shell> system
+system> ntp enable 10.0.0.1
+Starting ntp-enable 10.0.0.1
+.....
+Finished ntp-enable
+```
+
 ## Appliance maintenance
 
 ### Check OT monitoring services health
@@ -105,14 +150,14 @@ Use the following commands to show the current system date and time on your OT n
 
 |User  |Command  |Full command syntax   |
 |---------|---------|---------|
-|**admin**     |   `date`      |   No attributes      |
+|**admin**     |   `system date`      |   No attributes      |
 |**cyberx**  , or **admin** with [root access](references-work-with-defender-for-iot-cli-commands.md#access-the-system-root-as-an-admin-user)    |   `date`      |   No attributes      |
 |**cyberx_host**  , or **admin** with [root access](references-work-with-defender-for-iot-cli-commands.md#access-the-system-root-as-an-admin-user)    |   `date`      |  No attributes    |
 
 For example, for the *admin* user:
 
 ```bash
-shell> date
+shell> system date
 Thu Sep 29 18:38:23 UTC 2022
 shell>
 ```
@@ -128,16 +173,15 @@ To use these commands, make sure that:
 
 |User  |Command  |Full command syntax   |
 |---------|---------|---------|
-|**admin**     |   `ntp enable <IP address>`      |  No attributes |
+|**admin**     |   `system ntp enable <IP address>`      |  No attributes |
 |**cyberx**  , or **admin** with [root access](references-work-with-defender-for-iot-cli-commands.md#access-the-system-root-as-an-admin-user)    |   `cyberx-xsense-ntp-enable <IP address>`      |  No attributes      |
 
 In these commands, `<IP address>` is the IP address of a valid IPv4 NTP server using port 123.
 
 For example, for the *admin* user:
 
 ```bash
-shell> ntp enable 129.6.15.28
-shell>
+shell> system ntp enable 129.6.15.28
 ```
 
 ### Turn off NTP time sync
@@ -146,16 +190,15 @@ Use the following commands to turn off the synchronization for the appliance tim
 
 |User  |Command  |Full command syntax   |
 |---------|---------|---------|
-|**admin**     |   `ntp disable <IP address>`      |   No attributes      |
+|**admin**     |   `system ntp disable <IP address>`      |   No attributes      |
 |**cyberx**  , or **admin** with [root access](references-work-with-defender-for-iot-cli-commands.md#access-the-system-root-as-an-admin-user)    |   `cyberx-xsense-ntp-disable <IP address>`      |  No attributes |
 
 In these commands, `<IP address>` is the IP address of a valid IPv4 NTP server using port 123.
 
 For example, for the *admin* user:
 
 ```bash
-shell> ntp disable 129.6.15.28
-shell>
+shell> system ntp disable 129.6.15.28
 ```
 
 ## Backup and restore
diff --git a/articles/event-hubs/geo-replication.md b/articles/event-hubs/geo-replication.md
@@ -61,7 +61,7 @@ Geo-replication ensures disaster recovery and business continuity for all stream
 Geo-replication can be used to distribute data globally, allowing applications to access data from the nearest region. This reduces latency and improves performance for workloads located in different parts of the world.
 
 ### Data Sovereignty and Compliance
-Organizations operating in multiple countries often need to comply with data sovereignty laws that require data to be stored within specific geographic boundaries. Geo-replication allows these organizations to replicate data to regions that comply with local regulations, ensuring that they meet legal requirements while still maintaining a unified data platform.
+Organizations operating in multiple countries/regions often need to comply with data sovereignty laws that require data to be stored within specific geographic boundaries. Geo-replication allows these organizations to replicate data to regions that comply with local regulations, ensuring that they meet legal requirements while still maintaining a unified data platform.
 
 ### Migration and Upgrades
 Geo-replication can also be used to facilitate data migration, maintenance and system upgrades. Organizations can migrate their namespace proactively from a primary to a secondary region to allow for any maintenance and upgrades on the primary region.
diff --git a/articles/load-testing/how-to-schedule-tests.md b/articles/load-testing/how-to-schedule-tests.md
@@ -12,7 +12,7 @@ ms.topic: how-to
 
 # Define schedules on load tests
 
-In this article, you learn how to schedule load tests with Azure Load Testing. Scheduling tests allows you to run tests at a later time or run at a regular cadence. Azure Load Testing supports adding one schedule to a test. You can add a schedule to a test after creating it.
+In this article, you learn how to schedule load tests with Azure Load Testing. Scheduling tests allows you to run tests at a later time or run at a regular cadence. Azure Load Testing supports adding multiple schedules to a test. You can add a schedule to a test after creating it.
 
 ## Prerequisites
 
@@ -74,11 +74,11 @@ In this article, you learn how to schedule load tests with Azure Load Testing. S
 6. Select **Add** to add the schedule to the test.
 
 > [!NOTE]
-> If a scheduled test run is in progress when the next scheduled run is due, the next run is skipped. The next run will be scheduled for the next recurrence time.
+> If a scheduled test run is in progress when the next scheduled run is due, the next run is skipped. The next run will be scheduled for the next recurrence time. This happens only for test runs that overlap within a schedule. Overlapping test runs across multiple schedules are not skipped.
 
 ## View schedules
 
-You can view the schedule in the Schedule pane of the test. The schedule shows the next run time and the status of the schedule. You can have only one schedule in an active, paused, or disabled state. You can add another schedule after the current schedule is completed or deleted.
+You can view the schedule in the Schedule pane of the test. The schedule shows the next run time and the status of the schedule. You can have up to 50 schedules in an active, paused, or disabled state for a test. 
 
 You can view the trigger for a test run in the **Test runs** grid of the test. The trigger shows as Scheduled for a scheduled test run. You can filter the test runs grid to view only the scheduled test runs.
 
diff --git a/articles/migrate/toc.yml b/articles/migrate/toc.yml
@@ -69,6 +69,8 @@ items:
       href: resource-tagging.md
 - name: Create Business case
   items:
+  - name: Business case overview
+    href: concepts-business-case-calculation.md
   - name: Build a business case
     href: how-to-build-a-business-case.md
   - name: Review business case
