Benefit from Azure Arc-enabled SQL Managed Instance, even without a direct connection to Azure

This article is contributed. See the original author and article here.

Azure SQL Managed Instance is an intelligent, secure, and scalable cloud database service with the broadest SQL Server engine compatibility with all the benefits of a fully managed and evergreen platform as a service. With Azure Arc, you will now be able to deploy, manage, and monitor Azure SQL Managed Instance in an environment of your choice, outside of Azure. Azure Arc-enabled SQL Managed Instance has near 100% compatibility with the latest SQL Server database engine, and it will enable existing customers to lift and shift their applications to Azure Arc data services with minimal application and database changes while maintaining data sovereignty. 


 


Azure Arc-enabled SQL Managed Instance can be deployed at the edge, in your own datacenter, and in public clouds using Kubernetes and the infrastructure of your choice. Azure Arc-enabled SQL MI receives updates on a frequent basis, including servicing patches and new features similar to the experience in Azure. You will be able to scale your databases up and down dynamically in very much the same way you would do it in Azure, depending on the available capacity and resources of your Kubernetes clusters. 


 


Azure Arc-enabled SQL Managed Instance provides also other cloud benefits such as fast deployment and automation at scale. You will also be able to use familiar tools such as Azure portal, Azure Data Studio, and Azure CLI when you deploy, manage, and monitor your Azure SQL Managed Instance in your own environment, and you will be able to use tools like Azure Monitor for comprehensive operational insights across all your databases across hybrid and multicloud environments. 


 


Directly connected mode is one of the two different connectivity modes in Azure Arc-enabled data services. In this connectivity mode billing and inventory data is sent to Azure automatically. The data in your databases is never sent to Azure. 


 


How about a scenario where your data center does not allow connectivity to any public internet, or you have an edge location which does not have connectivity to the Internet, or the connectivity may be intermittent with long periods of outages?


 


In this scenario, you can deploy Azure Arc data controller in indirectly connected mode. Most of the services such as self-service provisioning, automated backups/restore, and monitoring can be run locally in your Kubernetes infrastructure. You would be using tools such as Azure Data Studio, Azure CLI, or Kubernetes native tools for self-service provisioning. Automatic upgrades and patching can be implemented by pulling the container images of Azure Arc-enabled SQL MI from Microsoft Container Registry, and pushing them to a local, private container registry that the data controller has access to. 


 


Indirectly connected mode supports automatic local backup and restore, and you can use the locally deployed Grafana and Kibana dashboards for monitoring. 


 


Read more about the connectivity modes of Azure Arc data services and try out Azure Arc-enabled SQL Managed in your own environment!


 


Marko Hotti


Sr. Technical Product Manager


Azure Arc-enabled SQL MI and SQL Server


Azure Data


 


 


 


 


 


 

3 ways to meet new hybrid expectations with Microsoft Teams and Microsoft 365

3 ways to meet new hybrid expectations with Microsoft Teams and Microsoft 365

This article is contributed. See the original author and article here.

Five years ago, we embarked on an exciting journey with Microsoft Teams, building a hub for collaboration and teamwork. Video meetings were not the workplace norm, but it was clear from the beginning that the combination of async and sync collaboration in a single product presented a unique opportunity to reimagine how we work, learn, and connect with others.

The post 3 ways to meet new hybrid expectations with Microsoft Teams and Microsoft 365 appeared first on Microsoft 365 Blog.

Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.

Feedback on Hotpatch, SMB over QUIC, and Extended Network in Azure Edition

This article is contributed. See the original author and article here.

Heya folks, Ned here again. We released Windows Server 2022 Azure Edition in November as part of Azure Automanage, which included the Hotpatch preview, SMB over QUIC, & Azure Extended Network features. In February, we also GA’ed the Hotpatch feature. We will soon be starting the Azure Edition Insider program, where you can get a preview of new features coming to in the first major release this autumn, including big changes to Storage Replica, SMB, and some surprises. After that, we’ll start the public preview of Azure Edition on Azure Stack HCI for on-premises private clouds.  


 


In the meantime, we are interested in your experience using this new operating system edition and the scenarios unlocked by these new features. If you’ve deployed Azure Edition, Hotpatch, SMB over QUIC, or Extended Network, we want to know how it went, what you liked, & what you need. We’re looking for direct experiences and with your consent, may want to chat with you further on a short phone call. 


 


You can send us an email at aefeedback@microsoft.com or just DM me directly here (just highlight my picture and click “message”). We’re very interested in hearing from you.


 


Until next time,


 


– Ned Pyle