Notice: Function Elementor\Controls_Manager::add_control_to_stack was called incorrectly. Cannot redeclare control with same name "color_menu_item". Please see Debugging in WordPress for more information. (This message was added in version 1.0.0.) in /home/site/wwwroot/wp-includes/functions.php on line 6121

Notice: Function Elementor\Controls_Manager::add_control_to_stack was called incorrectly. Cannot redeclare control with same name "color_menu_item_hover". Please see Debugging in WordPress for more information. (This message was added in version 1.0.0.) in /home/site/wwwroot/wp-includes/functions.php on line 6121

Notice: Function Elementor\Controls_Manager::add_control_to_stack was called incorrectly. Cannot redeclare control with same name "color_menu_item_hover_pointer_bg". Please see Debugging in WordPress for more information. (This message was added in version 1.0.0.) in /home/site/wwwroot/wp-includes/functions.php on line 6121

Notice: Function Elementor\Controls_Manager::add_control_to_stack was called incorrectly. Cannot redeclare control with same name "color_menu_item_active". Please see Debugging in WordPress for more information. (This message was added in version 1.0.0.) in /home/site/wwwroot/wp-includes/functions.php on line 6121

Azure SQL DB Failover Group Orphaned Users

I have a client  that resides in the Azure data platform arena, focusing mainly on Platform as a Service (PaaS) and Azure SQL DB.  They have a decent landscape of Azure resources and currently utilize failover groups within SQL DB to facilitate high availability.  Under the covers, failover groups are essentially Availability Groups and have […]