<\/p>\n
Monthly Azure news March 2022<\/p>\n
<\/h1><\/div>
In this blogpost you’ll read about the latest news from the Azure and Cloud-Native universe. We look forward to your comments, shares, engagement.<\/p>\n\n\n\n
Contents<\/p>\n\n\n\n
- \n
- New option available for Azure Static Web Apps configuration<\/a><\/li>\n\n\n\n
- Microsoft Azure helps to keep a sharp eye on the costs<\/a><\/li>\n\n\n\n
- Shutting down TLS 1.0\/1.1 for Azure DevOps is planned for March 31, 2022<\/a><\/li>\n\n\n\n
- New features available for Azure Chaos Studio<\/a><\/li>\n\n\n\n
- Preview of the new security feature for Azure API Management<\/a><\/li>\n\n\n\n
- Premium Tier finally available for Azure SignalR as a public preview<\/a><\/li>\n\n\n\n
- On-demand Compute Capacity Reservation has been shortly released<\/a><\/li>\n\n\n\n
- App Service Environment version 1 and 2 getting retired in August 2024<\/a><\/li>\n\n\n\n
- Azure DevOps Boards Modernization is available as an official public preview now<\/a><\/li>\n\n\n\n
- Azure Cosmos DB news<\/a><\/li>\n\n\n\n
- Azure Kubernetes Service news<\/a><\/li>\n\n\n\n
- Important information about Node.js versions<\/a><\/li>\n\n\n\n
- The new Azure Front Door is available now<\/a><\/li>\n\n\n\n
- Extended support for .Net Core 3.1 expires on 3 December 2022<\/a><\/li>\n\n\n\n
- Azure SDK retirement<\/a><\/li>\n\n\n\n
- Azure DevOps Artifacts support more upstream sources<\/a><\/li>\n\n\n\n
- Azure QnA Maker should be replaced through Question answering until March 2025<\/a><\/li>\n\n\n\n
- Application Insights: Support for instrumentation key-based global ingestion expires 2025<\/a><\/li>\n\n\n\n
- Support of multiple databases per data connection available now<\/a><\/li>\n\n\n\n
- The Terraform Azure Resource Manager Provider 3.0.2 has been released<\/a><\/li>\n\n\n\n
- We’re part a of Global <\/a>Azure <\/a>2022 in May<\/a><\/li>\n<\/ul>\n\n\n\n
<\/div>\n\n\n\nNew option available for Azure Static Web Apps configuration<\/h3>\n\n\n\n
Azure Static Web Apps provide a set of parameters that can be configured in the staticwebapp.config.json file. An additional parameter for specifying an API language runtime version has been released shortly. Here is an example of how to use the parameter:<\/p>\n\n\n\n
{\n \"platform\": {\n \"apiRuntime\": \"python:3.9\"\n }\n}<\/code><\/pre>\n\n\n\n
Supported values overview:<\/p>\n\n\n\n![\"\"](\"https:\/\/whiteduck.de\/wp-content\/uploads\/image-55-1024x420.png\")
Source: Microsoft<\/a><\/figcaption><\/figure>\n<\/div>\n\n\n Microsoft Azure helps to keep a sharp eye on the costs<\/h3>\n\n\n\n
Scheduling automated email alerts for changes on saved cost views will be available soon (currently in public preview). While subscribing to the changes there is a choice to choose between the daily, weekly, or monthly updates and an option for sharing the cost views with people outside the portal. For more information, please refer to the article<\/a>.<\/p>\n\n\n\n
Shutting down TLS 1.0\/1.1 for Azure DevOps is planned for March 31, 2022<\/h3>\n\n\n\n
The second attempt to turn off the weak standards TLS 1.0 and 1.1 will take place on March 31, 2022.<\/p>\n\n\n\n
The first attempt has been partially rolled back because of customers connected over the IPv4 endpoint (due to compatibility issues). Microsoft pointed out that only a low percentage of customers faced an impact and offered two test days for these customers where TLS 1.1\/1.0 has been turned off for half of the day to test the software. <\/p>\n\n\n\n
How to check the TLS 1.2 compatibility and how to enable TLS 1.2 are described briefly in this <\/a>blog post.<\/p>\n\n\n\n
New features available for Azure Chaos Studio<\/h3>\n\n\n\n
Azure Chaos Studio, a platform for simulating faults and outages via Chaos Engineering, has been extended by two new options:<\/p>\n\n\n\n
- \n
- Key Vault Deny access fault (preventing an application from retrieving content from the Key Vault)<\/li>\n\n\n\n
- Classic Cloud Services Shutdown fault (simulates service failure)<\/li>\n<\/ul>\n\n\n\n
All details of existing faults can be found here<\/a>. These faults can be added to an experiment. Now an experiment can be created using ARM templates or REST API. Microsoft is also going to introduce an experiment designer in the next weeks.<\/p>\n\n\n\n
Preview of the new security feature for Azure API Management<\/h3>\n\n\n\n
Azure Private Link enables private and secure communication between the customer\u2019s virtual network and the API Management gateway.<\/p>\n\n\n
\n![\"\"](\"https:\/\/whiteduck.de\/wp-content\/uploads\/Bild2.png\")
Source: Microsoft<\/a><\/figcaption><\/figure>\n<\/div>\n\n\n The main advantages are:<\/p>\n\n\n\n
- \n
- private access from Azure Virtual Network resources peered and on-premises networks<\/li>\n\n\n\n
- Built-in data exfiltration protection for Azure resources<\/li>\n\n\n\n
- Predictable private IP addresses for PaaS resources<\/li>\n\n\n\n
- Consistent and unified experience across PaaS services<\/li>\n<\/ul>\n\n\n\n
There are also some limitations due to the preview state of the feature: read in this article.<\/a> <\/p>\n\n\n\n
Detailed documentation on Azure Private Link can be found here.<\/a><\/p>\n\n\n\n
Premium Tier finally available for Azure SignalR as a public preview<\/h3>\n\n\n\n
Often asked features of the Premium Tier for Azure SignalR are available now as a preview – availability zone support, disaster recovery functionality, and autoscaling.<\/p>\n\n\n\n
Zone redundancy is enabled while creating or upgrading to a Premium tier resource (upgrading from Standard to Premium happens without downtime). More information about zone redundancy can be found here.<\/a><\/p>\n\n\n\n
Disaster recovery option offers multiple SignalR service instances and automatically switches to other instances when some of them are not available, described here<\/a>.<\/p>\n\n\n\n
Autoscaling option which is now available for the Premium Tier allows managing high load and idle times by adding or removing resources based on the defined rules.<\/a><\/p>\n\n\n\n
A short overview of the available SignalR tiers:<\/p>\n\n\n
\n![\"\"](\"https:\/\/whiteduck.de\/wp-content\/uploads\/image-56-1024x491.png\")
Source: Microsoft<\/a><\/figcaption><\/figure>\n<\/div>\n\n\n On-demand Compute Capacity Reservation has been shortly released<\/h3>\n\n\n\n
Both, Reserved Virtual Machine Instance (RI) and On-Demand Capacity Reservation, are relevant to Azure VMs. These features allow setting aside compute capacity in an Azure region for a defined duration of time. The main differences between On-demand Capacity Reservation and RIs are:<\/p>\n\n\n\n
- \n
- no long-running attachment to the reservation (RIs commitment lasts 1 or 3 years)<\/li>\n\n\n\n
- RIs \u201conly\u201d offer \u201ccapacity priority\u201d but no guarantee, On-demand Capacity Reservation provides a guarantee<\/li>\n\n\n\n
- On-demand Compute Reservation works with the pay-as-you-go principle (depends on the underlying VM size) whereas the long-term commitment of the RIs notably lowers the costs<\/li>\n<\/ul>\n\n\n\n
Documentation on how On-demand Capacity reservation works and what are current limitations can be found here<\/a>.<\/p>\n\n\n\n
App Service Environment version 1 and 2 getting retired in August 2024<\/h3>\n\n\n\n
7 months after the announcement of getting retired for the Azure Cloud Services (classic) Microsoft published a new update – App Service Environment version 1 and 2 will also retire in summer 2024. Starting March 2022 customers have a bit more than two years to migrate to App Service Environment version 3.<\/p>\n\n\n\n
A short comparison between the old and the updated version can be found here.<\/a><\/p>\n\n\n\n
Azure DevOps Boards Modernization is available as an official public preview now<\/h3>\n\n\n\n
The first attempt to release the public preview was done in November 2021. The feedback was not only positive as can be read in the comments to the first release announcement. So, the development team fixed a lot of reported bugs and is proud to announce another version of the \u201cNew Boards Hub\u201d, now as an official public preview. <\/p>\n\n\n\n
The customers are encouraged to try out the new Azure DevOps boards hub and to provide feedback about their experience. It will help the dev team to finalize the version which will be available as a final release this summer. A link <\/a>to a source.<\/p>\n\n\n\n
Azure Cosmos DB news<\/h3>\n\n\n\n
Finally, Always Encrypted for Azure Cosmos DB <\/a>is generally available. With this feature, sensitive entries will be encrypted before saving in the database. <\/p>\n\n\n\n
Another important feature that is currently in a public preview is the Azure Cosmos DB Partition Key Advisor notebook. It supports you while choosing the best partition key for the database workload. The advisor needs the information about the typical workload and some suitable keys to be able to analyze and rank the candidates Some further information find here.<\/a><\/p>\n\n\n\n
Azure Kubernetes Service news<\/strong><\/h3>\n\n\n\n
- \n
- Capacity reservation support is in public preview now.<\/a><\/li>\n\n\n\n
- Also in a public preview is the Azure Dedicated Host support for Azure Kubernetes Service. Dedicated Host offers a physical server (hardware isolation) for only your own virtual machines and provides you control over maintenance events.<\/li>\n\n\n\n
- AKS Node Auto drain: If an agent node has received a scheduled event (like Redeploy, Preemt, Terminate, or others) it will now be automatically drained by AKS to avoid unexpected disruption. Find more information here.<\/a><\/li>\n<\/ul>\n\n\n\n
Important information about Node.js versions<\/h3>\n\n\n\n
Node 14 LTS (long-term support) expires in one year on 30 April 2023. After the expiration date, the applications will keep running but no patches or services will be available for the unsupported version.<\/p>\n\n\n\n
Customers who are using Node 14 should update the applications to Node 16 LTS before the expiration date. Here is an overview of the Node.js lifecycle:<\/p>\n\n\n
\n![\"\"](\"https:\/\/whiteduck.de\/wp-content\/uploads\/Bild4.png\")
Source: nodejs.org<\/figcaption><\/figure>\n<\/div>\n\n\n The new Azure Front Door is available now<\/h3>\n\n\n\n
Azure Front Door has been announced by Microsoft as the enterprise content delivery network but due to some not covered customer demands the \u201cnew Azure Front Door\u201d has been released a couple of days ago. The new Azure Front Door offers two tiers \u2013 standard and premium.<\/p>\n\n\n\n
Do not be confused: the \u201cold\u201d Azure CDN is now called \u201cAzure CDN from Microsoft (classic), the \u201cold\u201d Azure Front Door is called now \u201cAzure Front Door (classic)\u201d, the newest release is called \u201cAzure Front Door\u201d.<\/p>\n\n\n\n
Key advantages of the new version are for example expanded Private Link support, Web Application Firewall, enhanced analytics and logging options, an easier cost model, and some more.<\/a><\/p>\n\n\n
\n![\"\"](\"https:\/\/whiteduck.de\/wp-content\/uploads\/Bild5.png\")
Source: Microsoft<\/a><\/figcaption><\/figure>\n<\/div>\n\n\n Extended support for .Net Core 3.1 expires on 3 December 2022<\/h3>\n\n\n\n
Applications that are hosted on Functions<\/a> will keep running but no important patches or services for the outdated version will be available \u2013 update the Functions to the runtime 4.x version (uses .Net 6) is required.<\/p>\n\n\n\n
App Service is affected by the .Net Core 3.1 support expiration as well. Applications that are hosted on App Service will continue running but again no support will be available. App Service applications should be updated to use .Net 6<\/a>.<\/p>\n\n\n\n
Azure SDK retirement<\/h3>\n\n\n\n
Older libraries are running out of support. To prevent issues due to missing security or performance updates to the Azure SDK, the outdated libraries should be upgraded to the newest version by 31 March 2023. For further information please refer to this article.<\/a><\/p>\n\n\n\n
Azure DevOps Artifacts support more upstream sources<\/h3>\n\n\n\n
A couple of days ago Microsoft announced<\/a> that Azure DevOps Artifacts now supports Google Maven Repository, Jitpack, Gradle Plugins, and PowerShell Gallery as upstream sources. This blog<\/a> describes how to enable one of them as an upstream source in a new or existing feed.<\/p>\n\n\n\n
Azure QnA Maker should be replaced through Question answering until March 2025<\/h3>\n\n\n\n
Customers who use Azure QnA Maker have (starting now) 3 years to switch from QnA Maker to the Azure Cognitive Service for Language feature called Question answering. Custom question answering offers the same features as the QnA Maker and some further options.<\/p>\n\n\n\n
Please refer to this article <\/a>to get more information about the required action.<\/p>\n\n\n
\n![\"\"](\"https:\/\/whiteduck.de\/wp-content\/uploads\/Bild6.png\")
Source: Microsoft<\/a><\/figcaption><\/figure>\n<\/div>\n\n\n Application Insights: Support for instrumentation key-based global ingestion expires 2025<\/h3>\n\n\n\n
Migration from Application Insights instrumentation keys to connection strings is required due to the end of support for instrumentation key-based global ingestion by 31 March 2025.<\/p>\n\n\n\n
Here is a detailed step-by-step guide for a successful migration.<\/a><\/p>\n\n\n\n
Support of multiple databases per data connection available now<\/h3>\n\n\n\n
Azure Data Explorer provides support for multiple databases per data connection. To use this option the connection should be first set as a multi-database data connection. It can be done in Azure Portal, using ARM template, C#, or Python. Please refer to the documentation<\/a> for more details.<\/p>\n\n\n\n
The Terraform Azure Resource Manager Provider 3.0.2 has been released<\/h3>\n\n\n\n
End of March HashiCorp published the new version of the Terraform Azure Resource Manager Provider. The new release contains a lot of features, enhancements, and bug fixes. For the upgrade information please refer to the official documentation<\/a>. <\/p>\n\n\n\n
The latest version can be found here.<\/a><\/p>\n\n\n\n
We’re a part of Global Azure 2022 in May<\/h3>\n\n\n\n
Join us at our on-site event after a long time in Stellwerk18<\/a> on May 7th. Our team will explain to you the development based on cloud native technologies such as Kubernetes or Azure services and show you how to modernize existing applications and develop new ones. Here we will explain the basics. You can then expand your knowledge in a hands-on manner in a prepared hands-on lab using realistic examples.<\/p>\n\n\n
- Capacity reservation support is in public preview now.<\/a><\/li>\n\n\n\n
- Microsoft Azure helps to keep a sharp eye on the costs<\/a><\/li>\n\n\n\n
![\"\"](\"https:\/\/whiteduck.de\/wp-content\/uploads\/global-azure-2022-banner-1.png\")
<\/a><\/figure>\n<\/div>","protected":false},"excerpt":{"rendered":"