New Relic by Organization Provisioning Error: "Bad Request. Errors reported by remote server: User tier changes are configured to be managed by New Relic, not the identity provider"
Dec 29, 2025
Okta Classic Engine
Okta Identity Engine
Okta Integration Network
Overview
New Relic by Organization app provisioning flow fails with the following error, visible in the Okta dashboard:
Automatic provisioning of user <username> to app New Relic by Organization failed: Error while trying to push profile update for: Bad Request. Errors reported by remote server: User tier changes are configured to be managed by New Relic, not the identity provider
Applies To
- New Relic by Organization
- Provisioning
- Error
Cause
New Relic SCIM server returned this error. As indicated in the error message, "User tier changes are configured to be managed by New Relic, not the identity provider," New Relic is set up to manage user tier changes, rather than allowing Okta (the identity provider) to update the attribute via provisioning.
Solution
- The New Relic app configuration in Okta should be verified to ensure that user tier attributes are not being updated via Okta, as these are managed within New Relic.
- To change a user's tier attributes, which are configured to be managed by New Relic, make those changes directly in the New Relic admin console.
- For User tier attributes managed by Okta, confirm that management permissions are enabled and that provisioning settings are aligned in both Okta and New Relic.
- Then, attempt the user provisioning again. Go to the Okta admin Console and navigate to Dashboard > Tasks. Any failed assignments should appear under Tasks.
- After identifying the failed task for the user that should be retried, click on Retry Selected.
- For detailed guidance on configuring SCIM provisioning for New Relic, please refer NewRelic's to the Configure SCIM provisioning from New Relic article.
- If the issue persists, please contact NewRelic support for more details and steps on how to resolve this error.
