Skip to main content

O365/Hybrid/Non-Hybrid Clients

I’m finding that with the retirement and introduction of infrastructure it’s a significant risk that we miss the addition or removal of a domain from Neo’s Company configuration; which in turn adds risk that our leaver processing agents may not secure accounts correctly as one example so my idea is below:

Pre-Req: An RMM or PSA integration active.

Idea: If Neo is aware of an active RMM/PSA integration, and see's a client connected for 365 only, it sends a singular probe (Monthly/Weekly?) to configuration items/active endpoints and looks for a server (or DC with or without the Entra Sync services depending how fancy we want to get). Then similar to the prompts you get for PRA roles being needed for GDAP, perhaps we can have another warning saying "Suspected domain" for those set to 365 only? 

So we get a visual warning that we may have missed a domain thus resulting in processes not being fully completed.

3 comments

Log in to comment and vote

Comments3

  • Gary Eastwood

    •

    Sep 21

    I’ve built into Neo a loopback process for Tool Failures where it flags tickets for review for itself where something hasn’t worked the way it was expected to - unable to add AD user for example, because AD has been decommissioned. In the review a second agent that is filtered down to only look at review tickets, it identifies the tooling error, what was actually done to get the user created, and then suggests improvements - this could be agent instructions, company memory, or even suggesting the company settings need updating.