
0
Under review
Test Connection operation for PowerShell connectors
Adrian Corston 4 years ago
in PowerShell connector
•
updated by Matthew Davis (Technical Product Manager) 1 week ago •
1
Most UNIFYBroker agents have a Test Connection operation, but this can't be configured for PowerShell connectors. This morning my customer's PowerShell connectors were failing because Azure was reporting the MS Graph API to be overloaded and only accepting admin connections (“53300: remaining connection slots are reserved for non-replication superuser connections”).
Add a Test Connection facility to a PowerShell connector. This would tie in with https://voice.unifysolutions.net/en/communities/6/topics/4220-scheduled-execution-of-test-connection-on-agents
Customer support service by UserEcho
A potentially better approach would be to add a PowerShell agent, and allow PowerShell connectors to consume that agent. This would give them access to the native Test Connection feature, and allow simpler powershell connector configuration as it can make use of agents.
Would this approach prove useful in any use cases?