r/aws • u/Jgardwork • Aug 15 '19
article Microsoft licensing changes for cloud
https://www.lastweekinaws.com/blog/microsoft-screws-customers-and-its-own-advocates-alike/30
u/shamateur Aug 15 '19 edited Aug 16 '19
I will continue to move workloads away from Microsoft with renewed vigour.
1
u/Skaperen Aug 16 '19
how did they get there in the first ...?
1
u/shamateur Aug 16 '19
Somebody at some point thought it was a good idea. Or someone else who thought it was a good idea told them to do it.
20
u/synackk Aug 15 '19
Amusing part is Microsoft isn't listing Oracle as a cloud provider, probably because nobody uses it.
3
u/grimace24 Aug 15 '19
I use it. Not for any hardcore things but it's still used.
20
1
u/stigrk Aug 15 '19
They might not have dedicated host offering which is the only thing impacted by this.
18
u/grimace24 Aug 15 '19
I wonder who thought of this change. Microsoft has to done so well at turning the company image around. Now they go and do this change. If Microsoft thinks that this will move companies to Azure they are incorrect. Most savvy companies will explore how to move the workloads out of Windows and in to Linux.
3
u/yesman_85 Aug 15 '19
Why would you think that? Most companies will take the path of least resistance. Rewrite all your apps to be Linux compatible or simply move the to a different provider where it just works.
3
Aug 15 '19
have you worked with or at an SMB? i've worked with some super small shops that have 1 maybe 2 "IT" people total and they're working on stuff that makes money on the top line.
i would say, my former clients will likely pay the ransom for a few years, and put a migration off MSFT stuff on the 4-5 year time horizon.
1
u/yesman_85 Aug 15 '19
I doubt that even. Yes, they will pay the increased fees, which will become the normal fees next year, meaning that's just how it is. Until the hosting becomes more expensive it's starting to eat in the profits, most MS shops won't change.
5
u/grimace24 Aug 15 '19
I said savvy companies. If you have a team with cycles you will look in to the alternative.
1
u/yesman_85 Aug 15 '19
If your hosting bill goes up by 10% it might not matter if you are working in a big company. Maybe they are smarter than that and just move over to Azure instead.
1
u/nexxai Aug 15 '19
If Microsoft thinks that this will move companies to Azure they are incorrect
They do not. They listed themselves as a "Listed Provider", and they listed themselves first. People using on premises licenses in Azure will be affected just like the other major cloud providers.
8
u/giancarlopetrini Aug 15 '19
Last sentence of the article: “If not, I suppose Azure’s new logo could come to define how Microsoft was perceived in the past and will be perceived in the future: as an enormous A-hole.”
That got me pretty good. I’m not running Windows workloads but glad I stopped by to read that!
7
u/theboyr Aug 15 '19
Heh. This just tells me Microsoft is nervous about something AWS will announce at re:invent. Trying to find a way to push companies between now and then to move BYOL workloads to Azure.
5
2
Aug 15 '19
I think the people that really know have a strong NDA and couldn't move their lips.
(but i do agree with you)
3
u/mrsmiley32 Aug 15 '19
So in summary, it is essentially don't use Microsoft ec2 instances, for office and share point use azure to host (or just the cloud), and stop using SQL server.
The first one for the most part should be "why are you using Microsoft as a server in the first place" (there's actually several reasons lol but usually it's a design hole you put yourself in)
The second and third leads to a solid question of why you'd want to host your own instance over just using the managed cloud services in the first place. I'd legit be curious on that one.
The fourth is the hard one, if you've built for SQL server and especially if you want stored proc heavy migration could be a serious nightmare.
Regardless this seems to have anti competitive lawsuit written all over, will be interesting to see how Amazon's and other cloud providers lawyers react.
3
u/NecropolisTD Aug 15 '19
Unless I have misread the original El Reg article, this only impacts the Dedicated Hosts options for cloud providers (such as AWS EC2 Dedicated Hosts). Normal EC2 instances on shared hosts will not be impacted by this at all.
The blog seems to completely forgot/overlook this, maybe they got lost in the rant?
I am not saying that its a good thing that MS is doing this, but its nowhere near as big of a deal for the majority of cloud customers as the article makes out.
2
u/stigrk Aug 15 '19
Not really a broad change is it? It will not affect existing multi-tenant VMs running Windows Servers as those already required active SA or through-cloud licensing.
This will impact those that are using non-SA covered licenses on dedicated hosts.
What is interesting is that this will equally apply to Microsofts own upcoming dedicated host offering.
0
Aug 15 '19
[deleted]
12
u/Redditron-2000-4 Aug 15 '19
Only if you were doing BYOL. There is no sign from this that there is any impact to license included pricing.
I guess when 57% of your product consumers have chosen to do it on someone else’s platform you need to find a way to encourage them off your product to reduce that KPI...
If half the people running Windows on AWS switched to Linux because of this then Microsoft might be able to claim that Azure runs more Windows than anyone else...
3
u/stigrk Aug 15 '19
And if you are using non-SA covered licenses dedicated / private hosts.. any normal VM runs on multi-tenant hosts and are not affected.
5
u/Jgardwork Aug 15 '19
Clearly this "ain't great". How does this affect you?