UNIFYConnect FAQs
Answers for deployment, integration, security, and operations.
Use these FAQs to understand where UNIFYConnect fits, how it connects to supported systems, and what operating model may suit your environment.
Common questions
UNIFYConnect is designed to fit the identity estate you actually have.
Customers usually want to know which systems are supported, which deployment model fits, how private-network connectivity works, and what security and support look like.
The answers depend on the source systems, target platforms, governance requirements, and operating model, but the patterns below cover the common decisions.
FAQs
Deployment and integration questions.
Supported systems
How UNIFYConnect connects identity sources and targets.
Which systems does UNIFYConnect support?
UNIFYConnect supports a growing catalogue of identity, HR, directory, and application integrations. See the supported systems page for the current catalogue.
Which corporate directories does it support?
UNIFYConnect supports Microsoft Entra ID, Active Directory, and other identity management platforms depending on the implementation pattern. If your directory is not listed, UNIFY can assess the integration requirement.
What do I need to have?
You generally need a corporate directory or identity platform, connected source or target applications, and approved connectivity between the systems involved in the workflow.
Deployment model
Choosing cloud, server, or agent-based connectivity.
Should I use UNIFYConnect Cloud or UNIFYConnect Server?
UNIFYConnect Cloud suits organisations that want a managed service with less infrastructure overhead. UNIFYConnect Server suits organisations that need to run the capability inside their own environment or operating boundary.
Do I need to install anything?
UNIFYConnect Cloud can connect to many cloud-based systems without customer-hosted platform infrastructure. For private-network or on-premises targets, UNIFYConnect Agent or another approved connectivity pattern may be required.
Where is the service hosted?
UNIFYConnect Cloud is hosted in Microsoft Azure. UNIFYConnect Server is installed within the customer’s own infrastructure.
Security and support
How the service is protected and operated.
How secure is the service?
UNIFYConnect is designed around tenant separation, encrypted communication, controlled access, and secure operating practices. Specific controls depend on the selected deployment model and customer requirements.
What makes UNIFYConnect better than building our own solution?
UNIFYConnect provides a supported integration and automation platform with reusable patterns, ongoing updates, operational support, and lower maintenance overhead than a collection of custom point-to-point scripts.
How do I avoid vendor lock-in?
Your investment remains in your identity and application platforms. UNIFYConnect is designed to adapt as systems, integration patterns, and platform roadmaps change.
How do I get support?
Support can include access to UNIFY knowledge resources, ticket tracking, expert assistance, health checks, and managed service operations depending on the engagement.
Readiness
Preparing for deployment and ongoing operations.
What do we get for the subscription fee?
Subscription inclusions depend on the service model, but commonly include access to identity integration capability, updates, support, troubleshooting, and operational recommendations for managed deployments.
Can UNIFY help with deployment readiness?
Yes. UNIFY can help with solution planning, configuration, directory and identity data readiness, security considerations, and deployment sequencing.
What warranty do we get?
Service-level commitments depend on the selected service and commercial arrangement. UNIFY can provide the applicable SLA position for your deployment model.
More questions