Skip to content

Commit 8e304fd

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into DICOMedits_Aug24
2 parents 6ee6fee + 2fc6615 commit 8e304fd

12 files changed

+2218
-9
lines changed

articles/automation/automation-create-alert-triggered-runbook.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Use an alert to trigger an Azure Automation runbook
33
description: This article tells how to trigger a runbook to run when an Azure alert is raised.
44
services: automation
55
ms.subservice: process-automation
6-
ms.date: 12/15/2022
6+
ms.date: 08/28/2024
77
ms.topic: how-to
88
ms.custom: devx-track-azurepowershell
99
#Customer intent: As a developer, I want to trigger a runbook so that VMs can be stopped under certain conditions.
@@ -102,7 +102,7 @@ To use Automation with alerts, you need a runbook that manages the alert JSON pa
102102

103103
As described in the preceding section, each type of alert has a different schema. The script takes the webhook data from an alert in the `WebhookData` runbook input parameter. Then, the script evaluates the JSON payload to determine which alert type is being used.
104104

105-
This example uses an alert from an Azure virtual machine (VM). It retrieves the VM data from the payload, and then uses that information to stop the VM. The connection must be set up in the Automation account where the runbook is run. When using alerts to trigger runbooks, it's important to check the alert status in the runbook that is triggered. The runbook triggers each time the alert changes state. Alerts have multiple states, with the two most common being Activated and Resolved. Check for state in your runbook logic to ensure the runbook doesn't run more than once. The example in this article shows how to look for alerts with state Activated only.
105+
This example utilizes an alert from an Azure virtual machine (VM). It extracts the VM data from the payload, specifically from the target resource of the triggered alert, and then utilizes that information to stop the VM. The connection must be set up in the Automation account where the runbook is run. When using alerts to trigger runbooks, it's important to check the alert status in the runbook that is triggered. The runbook triggers each time the alert changes state. Alerts have multiple states, with the two most common being Activated and Resolved. Check for state in your runbook logic to ensure the runbook doesn't run more than once. The example in this article shows how to look for alerts with state Activated only.
106106

107107
The runbook uses the Automation account [system-assigned managed identity](./automation-security-overview.md#managed-identities) to authenticate with Azure to perform the management action against the VM. The runbook can be easily modified to use a user-assigned managed identity.
108108

articles/communication-services/concepts/migrate-to-azure-communication-services.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -79,6 +79,8 @@ Azure Communication Services offers various call types. The type of call you cho
7979

8080
## Next steps
8181

82-
[Migrate from Twilio Video to Azure Communication Services.](../tutorials/migrating-to-azure-communication-services-calling.md)
82+
[Migrate from Twilio Video to Azure Communication Services](../tutorials/migrating-to-azure-communication-services-calling.md).
8383

84-
For a feature map, see [Calling SDK overview > Detailed capabilities](./voice-video-calling/calling-sdk-features.md#detailed-capabilities)
84+
[Migrate from Twilio Conversations Chat to Azure Communication Services](../tutorials/migrating-to-azure-communication-services-chat.md).
85+
86+
For a feature map, see [Calling SDK overview > Detailed capabilities](./voice-video-calling/calling-sdk-features.md#detailed-capabilities).

articles/communication-services/toc.yml

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -421,7 +421,10 @@ items:
421421
href: concepts/migrate-to-azure-communication-services.md
422422
- name: How to migrate from Twilio Video to Azure Communication Services
423423
href: tutorials/migrating-to-azure-communication-services-calling.md
424-
displayName: migration, migrate, Twilio, move, shift
424+
displayName: migration, migrate, Twilio, Twilio Video, move, shift
425+
- name: How to migrate from Twilio Conversations Chat to Azure Communication Services
426+
href: tutorials/migrating-to-azure-communication-services-chat.md
427+
displayName: migration, migrate, Twilio, Twilio Conversations, move, shift
425428
- name: Mobile integrations
426429
items:
427430
- name: Integrate with CallKit in iOS

articles/communication-services/tutorials/includes/twilio-to-acs-chat-android-tutorial.md

Lines changed: 397 additions & 0 deletions
Large diffs are not rendered by default.

articles/communication-services/tutorials/includes/twilio-to-acs-chat-csharp-tutorial.md

Lines changed: 397 additions & 0 deletions
Large diffs are not rendered by default.

0 commit comments

Comments
 (0)