Skip to content

Commit 650213c

Browse files
authored
Merge pull request #96875 from AbbyMSFT/patch-1
Edit the changes Noga made on this topic.
2 parents 479d001 + 101b86f commit 650213c

File tree

1 file changed

+8
-4
lines changed

1 file changed

+8
-4
lines changed

articles/azure-monitor/alerts/itsmc-dashboard-errors.md

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -97,15 +97,19 @@ The following sections describe common errors that appear in the connector statu
9797
* "Failed to add ITSM Connection named "XXX" due to Bad Request. Error: Bad request. Invalid parameters provided for connection. Http Exception: Status Code Forbidden."
9898
* "Failed to update ITSM Connection credentials"
9999

100-
**Cause**: The IP address of ITSM application isn't allow ITSM connections from partners ITSM tools.
100+
**Cause**: The IP address of the ITSM application doesn't allow ITSM connections from partner ITSM tools.
101101

102-
**Resolution**: In order to list the ITSM IP addresses to allow ITSM connections from partners ITSM tools, we recommend the to list the whole public IP range of Azure region where their LogAnalytics workspace belongs. [details here](https://www.microsoft.com/download/details.aspx?id=56519) For regions EUS/WEU/EUS2/WUS2/US South Central the customer can list ActionGroup network tag only.
102+
**Resolution**: To allow ITSM connections from partner ITSM tools, we recommend that the to list includes the entire public IP range of the Azure region of the LogAnalytics workspace. For more information, see this article about [Azure IP ranges](https://www.microsoft.com/download/details.aspx?id=56519). You can only list the ActionGroup network tag in these regions: EUS/WEU/EUS2/WUS2/US South Central.
103103

104104

105105
## Authentication
106106
**Error**: "User Not Authenticated"
107107

108-
**Cause**: There can be one of two options either the token need to be refreshed or there's missing integration user rights.
108+
**Cause**: This error can occur in two cases:
109+
- The token needs to be refreshed.
110+
- User integration rights are missing.
109111

110-
**Resolution**:If the integration worked for you in the past, it might be that the refresh token has expired. Then sync ITSMC to generate a new refresh token, as explained in [How to manually fix sync problems](./itsmc-resync-servicenow.md). If it never worked, it might be missing integration user rights, Please check it [here ](./itsmc-connections-servicenow.md#install-the-user-app-and-create-the-user-role)
112+
**Resolution**:
113+
- If the integration worked for you previously, the refresh token may have expired. [Sync with the ITSM Connector to generate a new refresh token](./itsmc-resync-servicenow.md).
114+
- If the integration never worked, it may be missing integration user rights. See the instructions to [install the user app and create the user role](./itsmc-connections-servicenow.md#install-the-user-app-and-create-the-user-role).
111115

0 commit comments

Comments
 (0)