Skip to content

Commit 3791597

Browse files
authored
Merge pull request #78854 from craigcaseyMSFT/vcraic0604
fixes for broken link report
2 parents 372c427 + b1e9218 commit 3791597

File tree

4 files changed

+6
-6
lines changed

4 files changed

+6
-6
lines changed

articles/active-directory/saas-apps/excelityglobal-tutorial.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -136,7 +136,7 @@ To configure Azure AD single sign-on with ExcelityGlobal, perform the following
136136

137137
### Configure ExcelityGlobal Single Sign-On
138138

139-
To configure single sign-on on **ExcelityGlobal** side, you need to send the **Thumbprint value** and appropriate copied URLs from Azure portal to [ExcelityGlobal support team](https://www.excelityglobal.com/contact-us/our-locations/). They set this setting to have the SAML SSO connection set properly on both sides.
139+
To configure single sign-on on **ExcelityGlobal** side, you need to send the **Thumbprint value** and appropriate copied URLs from Azure portal to [ExcelityGlobal support team](https://www.excelityglobal.com/contact-us). They set this setting to have the SAML SSO connection set properly on both sides.
140140

141141
### Create an Azure AD test user
142142

@@ -191,7 +191,7 @@ In this section, you enable Britta Simon to use Azure single sign-on by granting
191191

192192
### Create ExcelityGlobal test user
193193

194-
In this section, you create a user called Britta Simon in ExcelityGlobal. Work with [ExcelityGlobal support team](https://www.excelityglobal.com/contact-us/our-locations/) to add the users in the ExcelityGlobal platform. Users must be created and activated before you use single sign-on.
194+
In this section, you create a user called Britta Simon in ExcelityGlobal. Work with [ExcelityGlobal support team](https://www.excelityglobal.com/contact-us) to add the users in the ExcelityGlobal platform. Users must be created and activated before you use single sign-on.
195195

196196
### Test single sign-on
197197

articles/azure-monitor/platform/alerts-common-schema-integrations.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ This article shows you how to create a logic app that leverages the common alert
1515

1616
## Overview
1717

18-
The [common alert schema](https://aka.ms/commonAlertSchemaDocs) provides a standardized and extensible JSON schema across all your different alert types. The common alert schema is most useful when leveraged programmatically – through webhooks, runbooks, and logic apps. In this article, we demonstrate how a single logic app can be authored to handle all your alerts. The same principles can be applied to other programmatic methods. The logic app described in this article creates well-defined variables for the ['essential' fields](https://docs.microsoft.com/azure/azure-monitor/platform/alerts-common-schema-definitions#essentials-fields), and also describes how you can handle [alert type]('https://docs.microsoft.com/azure/azure-monitor/platform/alerts-common-schema-definitions#alert-context-fields') specific logic.
18+
The [common alert schema](https://aka.ms/commonAlertSchemaDocs) provides a standardized and extensible JSON schema across all your different alert types. The common alert schema is most useful when leveraged programmatically – through webhooks, runbooks, and logic apps. In this article, we demonstrate how a single logic app can be authored to handle all your alerts. The same principles can be applied to other programmatic methods. The logic app described in this article creates well-defined variables for the ['essential' fields](https://docs.microsoft.com/azure/azure-monitor/platform/alerts-common-schema-definitions#essentials-fields), and also describes how you can handle [alert type](/azure/azure-monitor/platform/alerts-common-schema-definitions#alert-context-fields) specific logic.
1919

2020

2121
## Prerequisites
@@ -119,7 +119,7 @@ This article assumes that the reader is familiar with
119119

120120
![Logic app expression](media/alerts-common-schema-integrations/logic-app-expressions.png "Logic app expression")
121121

122-
The ['monitoringService' field]('https://docs.microsoft.com/azure/azure-monitor/platform/alerts-common-schema-definitions#alert-context-fields') allows you to uniquely identify the alert type, based on which you can create the conditional logic.
122+
The ['monitoringService' field](/azure/azure-monitor/platform/alerts-common-schema-definitions#alert-context-fields) allows you to uniquely identify the alert type, based on which you can create the conditional logic.
123123

124124

125125
For example, the below snippet checks if the alert is a Application Insights based log alert, and if so prints the search results. Else, it prints 'NA'.

articles/iot-hub/iot-hub-event-grid.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ Azure IoT Hub integrates with Azure Event Grid so that you can send event notifi
2020

2121
## Regional availability
2222

23-
The Event Grid integration is available for IoT hubs located in the regions where Event Grid is supported. All device events except device telemetry events are generally available. Device telemetry event is in public preview and is available in all regions except East US, West US, West Europe, [Azure Government](/azure-government/documentation-government-welcome.md), [Azure China 21Vianet](/azure/china/china-welcome.md), and [Azure Germany](https://azure.microsoft.com/global-infrastructure/germany/). For the latest list of regions, see [An introduction to Azure Event Grid](../event-grid/overview.md).
23+
The Event Grid integration is available for IoT hubs located in the regions where Event Grid is supported. All device events except device telemetry events are generally available. Device telemetry event is in public preview and is available in all regions except East US, West US, West Europe, [Azure Government](/azure/azure-government/documentation-government-welcome), [Azure China 21Vianet](/azure/china/china-welcome), and [Azure Germany](https://azure.microsoft.com/global-infrastructure/germany/). For the latest list of regions, see [An introduction to Azure Event Grid](../event-grid/overview.md).
2424

2525
## Event types
2626

articles/iot-hub/iot-hub-message-enrichments-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ Message enrichments are available for no additional charge. Currently, you are c
7272

7373
## Availability
7474

75-
This capability is available in preview, and is available in all regions except East US, West US, West Europe, [Azure Government](/azure-government/documentation-government-welcome.md), [Azure China 21Vianet](/azure/china/china-welcome.md), and [Azure Germany](https://azure.microsoft.com/global-infrastructure/germany/).
75+
This capability is available in preview, and is available in all regions except East US, West US, West Europe, [Azure Government](/azure/azure-government/documentation-government-welcome), [Azure China 21Vianet](/azure/china/china-welcome), and [Azure Germany](https://azure.microsoft.com/global-infrastructure/germany/).
7676

7777
## Next steps
7878

0 commit comments

Comments
 (0)