Microsoft Entra ID (SaaS) Connector giving error

Hi Team,

I have connected an Entra ID connector in our lower environment but I keep getting the error below after having an app integration created. Any thoughts?

Error Received:

[cam-router]: [ConnectorError] Test connection failed: Provided source configuration already exists. Search for name:"Test_connection Source Failed" for more information. (requestId: f08c107659b749a8925f8e3f616e50c8) (requestId: f08c107659b749a8925f8e3f616e50c8)

Hi @P96337,

You’re able to make test connection successful ??

-Vasanth

Hi Vasanth,

Thanks for chiming in. I am not. I keep getting the error below.

Test connection failed: Provided source configuration already exists

When I search this is what I see

**long**

AZURE test connection failed with an error

**properties**

{"identityId":"CIEM_SYSTEM","identityName":"CIEM_SYSTEM","sourceName":"Microsoft Entra SaaS (CIEM connect)","tenantId":"575491f9-f156-450d-870d-f58e2d94e007"}

**reason**

Provided source configuration already exists

**short**

AZURE test connection failed

Hi @P96337,

I think it’s because of CIEM license, you may reach out to your CSM for getting this licenses.

You may refer this Azure Cloud Object Management

-Vasanth

Marvin, did you get this working? We are noticing the same error in our sandbox. We do not have CAM/CIEM setup for this connector so it is odd that it is getting a cam-router error.

Hello! I ran into a similar issue in a non-SaaS Entra source, but a different reason listed ({"message":"Unable to access Management groups, please verify management groups access"}).

To clear that up, I was able to go to the CIEM Settings tab of the source configuration, toggle Enable Cloud Infrastructure Entitlement Management (CIEM) on, Save, then toggle it back off, and Save again. After doing this, the issue went away for me. Might try something similar for your issue?

Hi Carl, I am still not able to get it connected. It is throwing a different error now - I am able to connect using the VA based connector with the Client ID and Secret - seems to be centered around the SaaS connector.

This source couldn't be connected due to an error.
Details

[Microsoft-Entra]: [ConnectorError] 401 Unauthorized (requestId: f8618166607d4d86a61e0771dce6ec97) | [cam-router]: [ConnectorError] std:test-connection Failed (requestId: f8618166607d4d86a61e0771dce6ec97) (requestId: f8618166607d4d86a61e0771dce6ec97)

Hi Corsillo, I was able to connect the VA based connector with no issue - just the SaaS connector is giving me an issue. Were you able to get the VA based connector to connect to CIEM and pull reports?

We aren’t using CIEM so I haven’t been able to test that. Sorry!

Thanks Mark, I tried that and it worked for me. Very odd.

1 Like

Any was able to fix this, We are having 2 different tenants connecting to 2 different Azure instances and we are also getting the same issue

Our Issue is resolved, We raised P1 ticket with SailPoint and worked with them to fix the issue

Marvin were you able to fix this? We aren’t using CIEM for Azure/Entra, but we are using CIEM for GCP. CIEM is working fine in our PROD tenant, but yesterday we tried to enable it in Sandbox, and received the same error that you got:

[cam-router]: [ConnectorError] Test connection failed: Provided source configuration already exists. Search for name: "Test_connection Source Failed"

hmmm - still getting the same error in my SB tenant as well. Is the feature enabled in your SB tenant as well?

Hi Mohan, What did they do to correct the issue?

Yes it is in our Sandbox tenant. I have a ticket open with Support.

Thanks Carl, I’ll do the same.

Carl - I have some info - for this error [cam-router]: [ConnectorError] Test connection failed: Provided source configuration already exists. Search for name: "Test_connection Source Failed" it appears a bug is causing this and they are working on pushing a fix to address it. In the interim - I am told - regardless of the error - the aggregations should complete successfully. I am seeing the aggregations complete successfully even though it is showing an error. CIEM collections occur every 24hrs so I won’t be able to see the collections until later but it’s a small bit of info I wanted to share. I didn’t receive word on when the fix will be pushed. Hope this helps.