Microsoft have always enjoyed a good name change and nowhere has this been more true than their rapidly growing security portfolio. You’ll be pleased to know the pace of change continues following Microsoft Ignite 2020!
What’s changed?
Old name
New name
Microsoft Threat Protection
Microsoft 365 Defender
Microsoft Defender Advanced Threat Protection
Microsoft Defender for Endpoint
Office 365 Advanced Threat Protection
Microsoft Defender for Office 365
Azure Advanced Threat Protection
Microsoft Defender for Identity
Azure Security Center Standard Edition
Azure Defender for Servers
Azure Security Center for IoT
Azure Defender for IoT
Advanced Threat Protection for SQL
Azure Defender for SQL
So gone are the various ATPs and Security Centers but now, like Marvel, we’ve got a bunch of Defenders to contend with!
There have also been a range of new features additions which will continue to strengthen Microsoft’s security offering including support for Amazon AWS and Google Cloud.
Only a few additions again this month but a couple are pretty interesting.
Azure DevOps Server 2020 is added.
Dynamics 365 Sales Premium is added. This is a new SKU that combines the “Sales Enterprise” and “Sales Insight” licenses for £101.80 per user per month – a saving of £7.50 pupm. Naming wise – I’m not sure that having an “Enterprise” SKU inside a “Premium” SKU really makes sense tbh!
Azure SQL Edge is added. This is a new variant of SQL made for the cloud world with features including:
Azure Stack Edge appears too – this is a physical device you keep on-premises, like a branch office or field location, to “filter, analyse, and transform your data before it moves to Azure”. Lose/damage one and it’s a $40,000 charge!
A new variant of SQL – Azure SQL Edge – is available in public preview and was added to the Product Terms in September 2020.
What is it?
This new flavour of SQL is made for the emerging, growing world of the cloud and edge computing – something of a focus for Microsoft over the last couple of years. Azure SQL Edge is based on SQL Server for Linux and, although it contains only a subset of the full functionality, it also includes features not found in SQL Server for Linux or Windows.
It supports both Intel and ARM processors and runs in containers, currently the only supported scenario is Docker hosts running Ubuntu 16.04 LTS or 18.04 LTS. New features include built-in data streaming and in-database machine learning.
When would you use it?
Microsoft say it is aimed at “edge scenarios” – primarily Internet of Things (IoT) – and it allows data to be analysed and processed before it gets to the central infrastructure; this can lead to faster results and also reduced cloud and network bandwidth utilisation. This latter point is an often overlooked aspect of working with the cloud – more data moving around more places means more network usage and, in many cases, more cost too.
“You don’t need an army of database administrators to install and manage SQL Edge on all your edge devices”
As Azure SQL Edge is container-based, you can deploy it from one portal and then simply update the container as needed. If this is indeed the case, it will help with the “do more with less” approach that comes with cloud – where you can easily end up with many more servers and assets than on-premises, without a matching increase in head count!
Pricing
It’s in Public Preview at the moment, meaning it can be used at no cost (in areas where Azure IoT Edge is available) and more details on pricing and purchase model will be released once the preview is over.
*Update – Feb 2025*
Unfortunately, Azure SQL Edge is being retired by Microsoft as of September 30th, 2025.
Microsoft recommend migrating to:
SQL Server Express
SQL Server Standard
SQL Managed Instance enabled with Azure Arc
None of which are particularly similar to the Edge edition.
Microsoft had, as expected, a great Q4 with revenue up 13% to $38 billion, which closed out an equally good fiscal year. Overall revenue of $143 billion, and operating income of $44.3 billion, was driven by revenue increases in all Microsoft’s key areas:
Office 365 was up 19%
Dynamics 365 was up 38%
LinkedIn increased by 10%
Azure was up 47%
Although the Azure growth was lower than previous quarters, it still seems healthy enough for now.
Microsoft called out some interesting points during their earnings call, some of which give a good indication of future direction including:
Slowdown in transactional licensing and flat on-premises server revenue: While this may be down, at least in part, to the impact of COVID-19 – it is also where Microsoft are heading. This is also shown by the fact that Office Commercial (on-premises Office) was down 34% -which Microsoft attributed to a combination of COVID-19 and the move to annuity licensing.
As long as those transactional licenses and on-premises server software are being replaced by CSP, Microsoft 365, and Azure – Redmond will be happy. I’ll be keen to see if this numbers start to rise again as the economic situation stabilises.
Bigger, longer Azure contracts: They stated “material growth” in Azure contracts over $10 million which is good news for Microsoft. For everyone in this new subscription based world, locking customers in to longer term deals is a key aim as it makes it easier for the vendor to forecast and budget.
Increased ARPU for Office 365: Average Revenue Per User (ARPU) is a key metric for many of today’s organisations and an increase means Microsoft are making more money per user. This could be as they upgrade to higher level plans (E3 to E5 for example) or purchase add-ons to their existing licenses. The Office 365 seat count increased and the ARPU increased, which are both positive for Microsoft.
All in all, a very positive performance from Microsoft that clearly shows their focus on cloud continues to pay off. Looking ahead to this financial year, FY 21, I think we’ll see more focus on E5 – particularly for security and voice workloads, Power Platform continuing to appear in new places, and increased pressure on those organisations looking to remain on-premises.
There was no English document available on the 1st when I did this (I guess the end of FY took it out of them 🤣), so I used the French version…my now 909 day Duolingo streak is coming in handy!
Nothing major changed or announced which is to be expected; being the start of their new financial year (and when everyone goes on holiday), July & August are often pretty quiet. What we’ve got is:
“System Center Configuration Manager” is renamed to “Microsoft Endpoint Configuration Manager”. The first real sign of anything happening with this new product name since it was announced a few months back.
“Azure Monetary Commitment” is now “Azure prepayment”.
If you have 1 or more licenses of Project Plan 1/3/5, all O365 users on that tenant get limited access to “Project for the web” customer data. No access to Power Platform apps and doesn’t apply to public sector.
June is the last month of Microsoft’s financial year but they’re still made a few changes worth noting in this month’s Product Terms:
5 year reservations for Azure VMs are added – with a 35% early termination fee
Azure Hybrid Rights for SQL have been expanded so now:
on-premises SQL Server Standard licenses can be used to run SQL Server Enterprise VMs in Azure
on-premises SQL Server Enterprise licenses can be used to run SQL Server Standard VMs in Azure
Changes to the eligibility for Office 365 and Microsoft 365 F1 & F3 licenses
SQL Server
The core conversion ratio is different for the two new scenarios:
4 x SQL Server Std on-prem cores w/SA = 1 x SQL Server Ent Azure core
1 x SQL Server Ent on-prem core w/SA = 4 x SQL Server Std Azure core
You can see the above table, and the info, on pages 54-54 of the June 2020 Product Terms.
F1/F3 changes
Microsoft have again changed the rules around who is eligible for a “Firstline” SKU. The new requirements are that to qualify for an F1/F3 license a worker must satisfy at least one of these conditions:
Uses a primary work device with a single screen smaller than 10.1”
Shares their primary work device with other qualifying Microsoft 365 or Office 365 Firstline Worker licensed users, during or across shifts
Other licensed Microsoft Firstline Worker users must also use the device as their primary work device
Any software or services accessed from the shared device requires the device or users to be assigned a license that includes use of those software or services
The previous guidance, updated in November 2019, was:
“A Dedicated Device is a computing device used for work with a 10.1” screen or larger, used by the user more than 60% of the user’s total work time during any 90-day period.”
These new rules should make it a bit easier for everyone to police but, for organisations already licensed for F1/F3 prior to June 1, 2020, you can continue to license based on the previous rules until your next renewal.
Microsoft have introduced their first vertical specific cloud offering – Cloud for Healthcare. Currently in public preview, the stated aims of this are to:
Enhance patient engagement
Empower health team collaboration
Improve insights
and, considering the current Coronavirus situation, focusing first on healthcare makes sense. They highlight that over 1,600 “COVID-19 bots” have gone live since March across 23 countries and we’ve already seen a huge rise in Azure usage during the last couple of months. The offering will span Azure, Microsoft 365, Dynamics 365 and more.
What’s next?
I look forward to seeing which other verticals are next to receive their own cloud and also, over the long term, if we start to see features and licensing differences between them. As cloud goes from being presented as one monolithic thing that everyone uses to separate, discrete offerings tailored to different industries, it will be much easier to introduce commercial differences. I imagine we’ll see some more about these at Microsoft Inspire in July.
There have been reports recently that some users in certain regions were hitting capacity limits in Microsoft Azure when trying to create new resources. Microsoft have shared some information around the impact the coronavirus epidemic is having on their cloud infrastructure:
775% increase in cloud services (in regions performing lockdown)
Teams up to 44 million daily users, running over 900 million minutes of meetings and calls each day
Windows Virtual Desktop (WVD) usage increased 3x
42% increase in government use of Power BI for sharing COVID-19 dashboards
Some of these numbers are pretty mind-blowing and one can see how they might catch a cloud vendor by surprise.
Cloud Datacentre provisioning
Microsoft say they will be adding “significant new capacity” over the coming weeks to help support this increased use.
Something I’m sure Microsoft have considered is how much of this extra usage will continue?. What happens as things start to return to normal and some of this usage starts to drop off? They’ll be left with more unused capacity than their models anticipated – might this lead to them raising prices on certain Azure services in the future?
Prioritising certain services
Microsoft have detailed that they’re focusing the “highest level of monitoring” on services related to emergency services, medical supply management, healthbots, and more.
They have also introduced some temporary restrictions to help ease the load – free offers are being limited, to keep capacity available for “existing customers”, and certain resources are being “soft” limited for new subscriptions. Customers can raise support tickets to raise these soft limits, but Microsoft do say that other geographical regions may need to be used to help manage demand.
Teams changes
Microsoft have made a number of small changes to Teams in an effort to reduce bandwidth. They scaled back how often it checks for people’s “presence” (whether they’re online or not), reduced the video resolution, limited how quickly it shows if the other user is typing, and made OneNote within Teams read-only for non-education tenants. All small changes that won’t really impact users but, collectively, must make quite a difference to the bandwidth being used.
Microsoft have been on a cloud push for 12 years now, since the launch of BPOS in 2008. They’ve been slowly “turning the ship” in various ways over the last decade, with the ultimate aim that as much of Microsoft is pointing at the cloud as possible. This is also a case of “trickle down (cloud) economics” – Microsoft are making their new direction reflect as much as possible within their partner base…and that change will then happen within Microsoft’s customers too.
Microsoft have made various changes to partner incentives, changed a few Software Assurance benefits related to training resources, and changed the Home Use Program – all aimed to drive cloud awareness in different ways. Their latest move is to retire all their on-premises server certification paths and exams related to the MCSA, MCSD, and MCSE qualifications that have been a staple of the Microsoft server world for years. The retirement date is June 30, 2020.
As you can see in this image from Microsoft, the recommended paths are now all cloud focused:
While not surprising given the focus on cloud, not just from Microsoft but across the industry, I do wonder if this is a little short sighted? There are still a LOT of on-premises servers in use and, with hybrid cloud being the de-facto way forward for most organisations, they will remain for a long time to come. Rightly or wrongly, this feels like Microsoft saying that they don’t care about on-premises anymore. I’ve seen MS people saying they’re still hiring lots of on-premises server engineers etc. and that may be the case, but this announcement will definitely be taken as a sign of their overall focus.
I’m often asked if Microsoft will continue to make on-premises versions of their software and, following this announcement, I can’t help but wonder if I need to rethink my answer…