No more action pack.

After reading through the actual Microsoft announcement the new usage terms aren't a whole lot different than how I interpreted the existing IUR.

  1. Product Licenses granted can be used for:

    • Demonstration purposes. Sales and marketing employees of the organization can use this

      software to showcase products to your customers, but demonstration products cannot be

      installed on customer hardware or infrastructure and must be used with partner supervision.

    • Solution/Services development purposes, including the development, testing and demos of

      solutions and services.

    • Internal Training can be used for training internal employees only. Use for customer training is

      not permitted.

    • Product licenses for internal use, in a development, test, demo, sandbox, or production

      environment for general internal business purposes and not for any type of commercial purpose.

      Product Licenses granted to partners cannot be used for:
    • Direct revenue-generating activities such as hosting a customer’s applications or development of

      custom solutions for a specific client

    • Employee personal use at home

    • Installation of solutions or services at a customer site

    • Customer training (except for learning partners)

    • Resell or transfer to any third party

It'll not change until next year this time so I'm sure we'll get more detail. At this point it doesn't look near as drastic as when they closed the Technet faucet.
 
How are you supposed to familiarise yourself with MS products / train staff in house / dry run customer installations / etc...
Wow, a sad day for future techs / tech biz.

*cough* Seems software piracy may get revived by stupid actions some never learn or finding a loophole like dvd rental companies, we'll see how it goes.
 
This isn't new... this is the way MAPS was way back in the day.

Here's the rub, how do they tell the difference between a demo solution and what you run in your office? I don't know about you guys, but I use my system to demo stuff all the time, my office network IS my demo.

But I can't use it to host anything that makes money for me directly. This isn't any different than I understood it before. More over, enforcement is almost impossible. So honestly, I don't see much to worry about here. I'm going to keep doing MAPS, and keep on trucking.

The support tickets have come and gone a few times through MS's history too, I've never relied on them being there. But now that everything is 365, most of the time I find I don't need them! 365 support does the lifting.

But there are companies out there that register, purchase a MAPS, and then use it internally and never bother to actually sell or support MS solutions. Those are the targets here, they've always been the targets. And there's always been fudge room for tiny shops where the lines between production and demo are merged.

Bottom line, make MS money, they'll leave you alone.
 
Last edited:
Here's the rub, how do they tell the difference between a demo solution and what you run in your office? I don't know about you guys, but I use my system to demo stuff all the time, my office network IS my demo.

It's pretty simple, if you're not licenced for the use you put it to, then you're outside of the terms of the licencing. If you use your demo system for purposes other than demoing than you need a licence that allows you to do more than demo.
 
This is actually going to cost us a lot of money. We were using this for our exchange cluster, and we're in talks about migrating to Office365 with the help of the 100 E3 licences that were previously available to us.
 
@trevm999 Then you're saying you're an Enterprise level customer, that want's a steeper than usual discount. This is precisely the use case that Microsoft is trying to nail down with these changes. They've never been OK with that, not in the almost 30 years I've been working with them. They're tolerant of tiny shops playing loose with MAPS a bit to get them going, because in the end that makes them more money. But somewhere along the line, you start buying the stuff you need for your own production separately and use the "free" seats for lab work.

But given the way 365 works, there really can't be a lab. So if they want me to pay for it, I'll do that. The MAPS subscription for my 5 seats of E3 is about the same as the annual cost of E3, and I'll just use different subs to fill the gaps to get the price down. I know several other MSPs that never went in for the free seats and just bought what they needed. Microsoft is now saying that is the correct path forward.

Again, I've seen them do this in the past. And I expected them to do it again. MAPS was never "OK" for internal use. There's a bit of a grey area for tiny operations, but that's it. If you've got 100+ E3 seats, you're simply an enterprise customer. Your margin you get for selling Microsoft's platform is your reward for selling it. Which is the same thing for me... I have to pay for all my software too. So again, for my part these MAPS changes don't mean jack to me, it won't change the way I use MAPS at all. I'll call my rep next week, and he'll probably confirm all of this with me because again MS has been here before.

But the big rub, are the companies that use MAPS for their on direct gain... that's never been OK. Internal use is exactly that... INTERNAL. If it's publicly accessible, it's not internal.

It's also possible a backlash will make them change their minds... again... Time will tell.
 
After reading through the actual Microsoft announcement the new usage terms aren't a whole lot different than how I interpreted the existing IUR.



It'll not change until next year this time so I'm sure we'll get more detail. At this point it doesn't look near as drastic as when they closed the Technet faucet.
Ok, that is not any change that I can see. You could always use the NFR for internal use. You never could run services and sell them like your own webserver or exchange server but for internal use to run workstations in your office. That is still allowed.
 
@Sky-Knight We're an application developer and don't make any money off of making our applications dependent on Microsoft, it actually raises the total end cost for our clients. MPN helped up stay blissful ignorant of the true cost of using Microsoft products.
 
@trevm999, then I'd say Microsoft did the world a favor. O365 is the only SaaS solution that's actually worth the money. Every single other attempt I've seen, patently isn't. So now that you know what it costs, you can change gears and do what the majority of the rest of the planet has done...

Swap to Linux...

And if that idea seems to be more expensive, then you've just found out how you are indeed making money making your applications dependent on Microsoft.

I'll bet if you dive in there and look, you'll find value all over the place. But I wouldn't be surprised if you discovered you need to switch too.

I mean for crying out loud... in some cases Microsoft is abandoning Microsoft... https://www.zdnet.com/article/linux-now-dominates-azure/
 
Back
Top