CTT Big4 News Azure Recently #MS006

CTT Big4 News Azure Recently #MS006

Hello Friends, welcome to CTT News – Big4 Recently

AWS, IBM, Google & Azure – the Big4 Cloud Service providers are improving and introducing very frequently and it is hard to keep up to date ourselves without single source of information. Hence, in this series, we intend to address most important recent news of Big4 Cloud Platforms. You may save your valuable time by not searching recent updates of these cloud platforms from different individual websites. We hope, you will find this series interesting. Please visit specific Cloud provider news that you are interested in as following.

In this article, we will explore latest Azure Recently. So, lets jump on the updates.

Azure SQL Database Update

Flexible new way to purchase: 

Azure has announced the preview of an additional purchasing model with Azure SQL Database Elastic Pool and Single Database deployment options.

Recently announced with SQL Database Managed Instance, the vCore-based purchasing model reflects our commitment to customer choice by providing flexibility, control, and transparency. As with Managed Instance, the vCore-based model makes the Elastic Pool and Single Database options eligible for up to 30 percent savings with the Azure Hybrid Benefit for SQL Server.

Long-term backup retention: 

The preview of long-term backup retention in Azure SQL Database, announced in October 2016, has been updated with a set of major enhancements based on customer feedback:

  • More regional support. Long-term retention will be supported in all Azure regions and national clouds.
  • More flexible backup policies. You can customize the frequency of long-term backups for each database. Policies cover weekly, monthly, and yearly backups, with specific week-within-a-year backups.
  • Management of individual backups. You can delete backups that are not critical for compliance.
  • Streamlined configuration. There’s no need to provision a separate backup service vault.

Scale-out support

Azure SQL Database is further expanding the power of databases and elastic pools by including read scale-out support in the Premium and Business Critical service tiers. 

This capability redirects the read-only client connections to one of the automatically provisioned HA replicas and effectively doubles the compute capacity of the database or elastic pool at no additional charge. This is ideal for load balancing of complex analytical workloads without affecting the primary OLTP workload.

GUID migration: Azure Service Bus

Azure Service Bus connects your existing on-premises systems to cloud solutions, distributes messages to multiple independent back-end systems, and simplifies enterprise integration with reliable cloud messaging.

Starting on May 1, 2018, you’ll be billed at an hourly rate for Service Bus standard base units and Service Bus premium messaging units. This replaces the current daily and monthly rate billing, making it more consistent with other Azure services. Pay only for the number of hours you use Service Bus, rather than for a whole day or month.

All Azure Service Bus customers will be migrated to new GUIDs. There won’t be a pricing impact from this change, but you might need to modify billing routines that rely on resource GUIDs. See the following table for GUID migration details.

Deployment Groups and build completion trigger – VSTS Sprint 132 Update

The Sprint 132 Update of Visual Studio Team Services (VSTS) brings a few key features to help you scale your build and release pipeline.

For build, use the new build completion trigger to chain together related builds that might be owned by different teams. For release, the Deployment Groups feature is generally available. You can use it to scale deployments across multiple virtual machines with high availability, including production environments.

Other highlights include:

Microsoft peering on ExpressRoute Standard SKU now available

Microsoft peering with route filters is now available for Azure ExpressRoute Standard SKU. You can access Azure PaaS services, such as Azure SQL Database and Azure Storage, that are offered on a public IP address within the geopolitical zone of your ExpressRoute circuit. 

As a result of this new functionality, can no longer create new Azure public peering configurations. Existing Azure public peering configurations will continue to be supported, though it is recommended moving to Microsoft peering with route filters. 


Author: Debashree

A Technical writer and passionate about digital life. Always eager to learn and share knowledge.

2 Replies to “CTT Big4 News Azure Recently #MS006”

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.