this post was submitted on 15 Nov 2024
162 points (100.0% liked)

Technology

59673 readers
3915 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 15 points 1 week ago* (last edited 1 week ago) (3 children)

Weird...very weird. AWS owns nearly ~~50%~~ over 30% of the web, but they're going after MS for a shitty product (Azure), which is at 20-25%

[–] riskable 22 points 1 week ago (2 children)

The article sucks. The FTC isn't going after Microsoft's cloud services because they're good/bad. They're going after Microsoft because of forced bundling. Same abuse of monopoly power they were found guilty of when they started forcing everyone to use Internet Explorer.

Microsoft is forcing customers to use their cloud services under all sorts of scenarios. Many of which have no logical reason other than to force customers into Azure.

For example, if you have a lot of Windows servers in Azure they will stop supporting you once you reach a certain threshold unless you also sign up to use their enterprise cloud AD service.

They already do this with regular Windows--you have to use AD if you're a business customer and you go past a certain threshold of systems--but in that case you can just get some Domain Controllers and call it a day. You can put them wherever you want (locally, in AWS, in Azure, wherever).

With Azure Windows servers though you're forced to use Azure AD (or you lose support and possibly access to other bundled services). You can't host Domain Controllers anywhere else. I mean, they'll let you have as many off-Azure DCs as you want but they must still be joined/synchronizing to Azure AD.

There's probably many other anticompetitive tactics in place within the world of Azure but that's the one big one I know off the top of my head.

[–] [email protected] 1 points 1 week ago

you do not have make local DC join to Azure wtf are you talking about

[–] [email protected] 1 points 1 week ago

Dunno...I'm not saying Microsoft isn't doing bad things...I'm just saying they wouldn't be my priority.