Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
3rd party Azure IDP configuration fails with " The user you specified is not authorized to perform this action" - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • 3rd party Azure IDP configuration fails with " The user you specified is not authorized to perform this action"
KB0744390

3rd party Azure IDP configuration fails with " The user you specified is not authorized to perform this action"


872 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

Symptoms

When you try to Configure sign-on from Azure portal but it fails with an error " The user you specified is not authorized to perform this action" .

 

Below is an example of the menu when configuring in Azure:

Setting servicenow on Azure

 


Cause

From the instance System Log >ALL

we see the below message:

 

java.sql.BatchUpdateException: Duplicate entry 'http s://sts.windows.net/<id>/' for key 'idp'

: java.sql.SQLException: java.sql.BatchUpdateException: Duplicate entry 'http s://sts.windows.net/<id>/ for key 'idp'


This indicate there is already an Identity Provider URL entity ID with the same name in the Identity Provider record of the Instance.

Resolution

 

To resolve the problem, from the logs, identify the duplicate Identity Provider. Then find and delete the duplicate record from the Instance Identity Provider record and try again to add it on the Azure console.


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.