YSoft SafeQ in Public Cloud - Microsoft Azure
Leveraging Azure Platform
YSoft SafeQ is fully deployable in Microsoft Azure, to take advantage of the increased scalability, availability and reliability.
Azure SQL
Leveraging cloud database as a service is available with YSoft SafeQ.
Please note that Azure SQL support is currently available under Early Access Program.
Azure Active Directory Domain Services
Azure Active Directory Domain Services, domain controller as a service, can be utilized for identity management. LDAP(s) protocol is used for user metadata synchronization and user authentication.
Integration with Azure AD via OpenID Connect
You can set up integration with Azure AD via OpenID Connect so that the users can authenticate to YSoft SafeQ management interface with their Azure AD credentials. Furthermore, you can set up this integration in a way that user accounts in YSoft SafeQ are managed by an external Identity Provider (in this case, Azure AD). For the details and the limitations of this integration, see .Integration with external Identity Providers via OpenID Connect v6.0.65.
Azure Load Balancer
YSoft SafeQ can leverage load balancing and failover on several places in the architecture. Azure Standard Load Balancer can be utilized.
Azure Standard Load Balancer is only limited to monitor one port for health probe. This limits its capabilities for fault detection.
Power BI
Power BI integration is fully supported and available. For documentation how to implement and use provided template, refer to Power BI connection manual.
Monitoring
For more details about YSoft SafeQ application monitoring, refer to a dedicated document YSoft SafeQ Performance and Availability Monitoring Guidelines.
Scaling
YSoft SafeQ currently does not support automatic vertical nor horizontal scaling as implemented in Azure. For Azure scaling, refer to Microsoft Documentation https://docs.microsoft.com/en-us/azure/monitoring-and-diagnostics/monitoring-overview-autoscale
Docker on Azure
YSoft SafeQ currently cannot be containerized in Docker.
Best Practices
Always secure the YSoft SafeQ installation following System communication hardening documentation.
Print queues shared from servers prove to be less maintenance intensive (= less expensive), compared to any components deployed on client workstations.