O365 connector for government tenant

Feedback Integration Service
,
1

My organization has recently migrated to Microsoft government tenant which caused all automations using the O365 connector for previous tenant to fail. I’m looking to see if anyone has ideas regarding next steps, either create a new custom connector or if there is a way to somehow start with the current O365 connector as a baseline and modify the URIs it uses as endpoints.
We heavily rely on the triggers portion of Integration Service which is why we would like to stay in this realm of solutions.

3

@Sean_Tosloskie

You can modify or create a new connection to your new office 365 tenant and allow the 3rd prty consent apps

Cheers

5

Thank you for the reply, however I seem to be running in to an issue when I select the “Add Connection” button for a new O365 connector. When I select this it takes me to the Select Account menu for Microsoft, but I noticed it is pointing to our old commercial AD tenant’s client_id. How is this client ID configured?

image
image782×35 2.63 KB

The above shows our old client_id in the URL, this needs to point to our new tenant’s client_id. Once we select an account, it takes us to our .us tenant and we receive the error that the old client id in the URL is not found in our tenant, which makes sense. How can this be modified to contain our new client id?

6

Hi @Sean_Tosloskie

The configuration for the client ID of the O365 connector is typically handled through the Orchestrator settings. To modify the client ID to point to your new tenant, you need to update the configuration in the Orchestrator.

Here’s how you can update the client ID for the O365 connector in UiPath:

  1. Open the UiPath Orchestrator web interface.
  2. Sign in with your credentials.
  3. Navigate to the “Settings” page or the “Admin” section.
  4. Look for the O365 connector settings or the settings related to the Microsoft activities package.
  5. Locate the field or configuration related to the client ID.
  6. Update the client ID with the new value corresponding to your new tenant.
  7. Save the changes.

Once you have updated the client ID in the Orchestrator settings, the O365 connector will use the new client ID when you attempt to add a connection. This should resolve the issue you’re facing with the incorrect client ID pointing to the old tenant.

7

Thank you for your reply. I am unable to locate anything related to step 4, mentioning anything regarding O365 connector. Are you able to provide a screen shot?

8

Any other ideas? It seems like the last response was a chat GPT result which may not be factual. There doesn’t seem to be any related area for that modification.