Managing credentials has long been one of the more frustrating (and risky) parts of cloud integrations.

From storing client secrets to handling expirations and access control, it adds unnecessary overhead for teams that just want their systems to connect reliably and securely.

That’s why we’ve introduced support for Managed Identity authentication in GK Integrator, alongside the existing Service Principal method.

What’s changed?

GK Integrator now allows you to choose between:

• Service Principal authentication (existing method)

• Managed Identity authentication (new)

This added flexibility means you can align your integration setup with your organisation’s security and infrastructure preferences.

Why it matters

Improved security
Managed Identity removes the need to store and manage client secrets, reducing exposure and risk.

Less administrative overhead
No more manual secret rotation or credential management.

Simpler configuration
Authentication is handled directly by Azure, making setup and ongoing maintenance easier.

Aligned with best practices
Supports a more modern, cloud-native approach to integration design.

Where this applies

This enhancement is particularly valuable for organisations running integrations within Azure environments, helping streamline how systems connect while strengthening security posture.