Looks like Microsoft has updated Security Defaults on October 14th.

Instead of the all or nothing setting that exists now, individual controls for MFA, legacy authentication, and device code flow would be available.

At present, it is in private preview for some tenants.

A pretty cool update for us who have many Business Basic/Standard tenants.

https://learn.microsoft.com/en-us/entra/fundamentals/security-defaults#manage-individual-security-defaults-protections-preview

We are affected by this and contacted support. Others are affected as well and are also creating support tickets. Status page was just updated as I type this: https://smtp2gostatus.com/

XPosting

Hey all, I know job posts aren’t really a thing in here so go easy on me. Mods pull it if its not ok.

I owned an MSP for a long time before I started Synthreo where we build AI stuff for MSPs. We’re looking for people who just love AI and have been messing around with Claude Code or Cursor or whatever and building things on the side and want to play with this stuff for a living. Doesn’t matter if your a tech, a vCIO, or a former MSP owner yourself. You don’t need to be a developer, our agentic harnesses do the heavy lifting. We need people who know what the end result should look like because they’ve lived it, and honestly MSP people are better at that than most devs I’ve worked with.

Here’s the link if your interested https://www.linkedin.com/jobs/view/4479141957/ and if you have questions just DM me.

We don’t seek out project-only work, and don’t get serious inquiries about it. Those non-serious inquiries tend to be the fewer than five user businesses, or people who want a post-breach quick fix.

We just got a request from a 15-person business who has done DIY IT so far, to migrate email and a file server to 365, and get Claude connected to 365 properly.

They’re not opposed to fully managed service, and the DIY IT person (who is a co-owner) doesn’t really want to do IT anymore.

I can’t decide if we quote this migration and the usual managed services, and insist that we only do the migration as part of bringing them aboard as fully managed. Doing the migration only and waiting for them to mess something up, or having to provide post-migration support with the clock running are both completely unappealing to me.

How do you all generally handle these kinds of opportunities? They’re a good fit ICP-wise.

How are Customer Success Managers and CSM teams using HaloPsa? What are the workflows, ticket types and ticket categories you have in place? Looking for any best practices and recommendations to set up our halo environment for a CSM team of 2 people managing 20-40 clients and growing. We are starting from scratch with our Halo implementation and currently have just been using the very basic ticket workflow that our MSP engineers use where every ticket is an "incident". It is not an ideal process to handle meeting action items, procurement orders, qbr prep, opportunity identification, renewal processing, onboarding, etc. Any insight is appreciated!

Logged into Inky this AM and saw the AI recommendations beta and went through a few and they were legitimately helpful and accurate. That is now two vendor AI's that i find useful, and both are built into and hyperfocused on that product vs a wider LLM (DefensX is the other).

I chatted with my old Inky rep a bit back (they've moved up and are still there) and i have to admit i still like where the product is going.

Edit: The main point i forgot to really address is in a sub-comment below:

...I kind of called out like a year ago is: AI is more useful to the SMB in a focused, applied way vs bolting on a generic LLM to the toolset. Not that the common bolt-on method isn't useful, but the only two vendors where I've used their own AI INSIDE the toolset have been immediately helpful.