Microsoft adds Azure AD Join to Windows 365 Cloud PC

Fancy some Windows 365 Cloud PC in your life, but less than keen on throwing yourself into the world of Azure infrastructure? Microsoft has added AD Join as a Cloud PC join type option. Exactly why you'd want a Cloud PC is entirely different matter. We weren't impressed with what we saw last year as it wasn't the snappiest …

[Pascal Monett]

Oh goody

I wonder how long that will take to fall over.

[Zippy´s Sausage Factory]

Re: Oh goody

Knowing Microsoft, they'll announce its replacement in a few weeks, but keep supporting it for the next ten years just because they're not really sure whether anyone's still using it or not.

[ShadowSystems]

I'm confused.

Why would you want to turn a desktop computer with an OS, local file storeage, local security, & essentially zero lag into a glorified VT terminal using someone else's hardware, someone else's file stores, someone else's (lack of) security, plus network latency instead?

That's akin to owning a perfectly fine estate car in your garage, but paying someone else to drive you around in a falling-apart-at-the-seams clunker "to prevent wear & tear on my own stuff".

What's the point, from the customer's point of view, of cloudy DAAS?

[BizDev]

Re: I'm confused.

Benefit to cloudy DAAS - from the customer's point of view this permits off site or out of office working, but allows us to maintain controls on the data/keep it on-site - for example one of the effects of the pandemic for my organisation was the sudden requirement to hook up thousands of laptops etc that belonged to end users to the network in order for them to be able to run desktop software that was previously safely installed in the office.

To get round the issues this presented, a number of users suddenly had a crash course in using remote desktops as there was no way we could install to end user owned machines and maintain compliance (also it would have taken ages!)

Of course - that was DAAS on _our_ infrastructure - as you say, moving that use case to somebody else's data centre brings its own compliance and security issues...

[ShadowSystems]

Re: I'm confused.

Ok, using your own in-house hardware so remote workers (such as WFH) can log in via their own kit, but use their work-housed desktops I can understand.

You keep your corporate data/resources as secure as you can, allowing for remote workers to mitigate any MITM attacks if at all possible.

It's the ones that use someone else's hardware, someone else's (lack of) security, & retain essentially zero control over their own data that boggles my mind.

Thanks for the attempt to clarify. =-J