WaelHamze

@jblaseske did you try to set RequireNewInstance = true in the connection string https://docs.microsoft.com/en-us/power-apps/developer/data-platform/xrm-tooling/use-connection-strings-xrm-tooling-connect#connection-string-parameters

@frick-brian are you still facing issues with this?

@devkeydet I think having a consistent way of connecting would make it easier for consumers. However there is a draw back... The Power Platform connection is a special type. Need...

@devkeydet @mattp65 thanks for the useful feedback... @devkeydet please let us know once you have discussion with the Power Platform Build Tools team.

@devkeydet / all Thanks for looking into this. Regarding separation of concerns, if I am not mistaken, service connections use libraries under the hood. So whether you storing secrets in...

@nikolacace what is not good about using the app registration as part of the connection? "AuthType=ClientSecret; url=https://contosotest.crm.dynamics.com; ClientId={AppId}; ClientSecret={ClientSecret}"

@saiankith-explorer Are you getting any errors from the upgrade operation? I notice one of the solutions is a patch not sure where this comes from. Normally you can do two...

@saiankith-explorer did you try to run the upgrade from the maker portal UI? Does this work? (Does it remove the upgrade solution and the patches) I have tested this today...

@bfallar3 the agent needs to have line of sight to the Dynamics instance. Do you have some sort of IFD setup that allows you instance to be accessible from outside...

@bfallar3 in this case there could be two issues 1- connection string is incorrect 2- you may need to configure or bypass the proxy on the self hosted agent