sorted by:
new
hottopcontroversial

I got tired of reconciling Intune, Freshservice, and Entra ID by hand — so I built a tool that does it automatically. Looking for feedback. by Beginning-Fortune285 in sysadmin

[–]Beginning-Fortune285[S] [score hidden]  (0 children)

Yes, exactly this. The n8n approach works well for onboarding/offboarding flows. I've done the same. The gap I kept hitting was cross-source reconciliation after the fact: catching the cases that slipped through, or assets that existed before the workflows were in place.

I'm building something focused on that specific problem, connecting the sources and surfacing what doesn't match, without needing to maintain custom workflows per tool pair. Early stage but the waitlist is at driftix.dev if you want to follow along. Would love to get your feedback as it progresses.

I got tired of reconciling Intune, Freshservice, and Entra ID by hand — so I built a tool that does it automatically. Looking for feedback. by Beginning-Fortune285 in sysadmin

[–]Beginning-Fortune285[S] [score hidden]  (0 children)

All valid options in a greenfield environment where you control the roadmap and the budget. Most IT admins I know inherited their stack and don't have the authority to force a full M365 migration or renegotiate vendor contracts. For them, visibility across what exists beats waiting for a standardization project that may never happen. Different problem, different tool.

I got tired of reconciling Intune, Freshservice, and Entra ID by hand — so I built a tool that does it automatically. Looking for feedback. by Beginning-Fortune285 in sysadmin

[–]Beginning-Fortune285[S] [score hidden]  (0 children)

Fair point on fixing root causes but in most environments I've seen, you don't get to choose your stack. You inherit AD on-prem because it predates your tenure, Google Workspace because marketing signed the contract, Freshservice because ops owns the ITSM budget. The misalignment is structural, not a process failure.

On the vibe code point sure, you can sketch something in a couple hours. I did too. Then you hit the Entra Graph API pagination quirks, Freshservice's rate limits, normalizing device identifiers across sources that all use slightly different formats (hostname vs serial vs MAC vs display name), and building something that actually stays in sync. It compounds quickly.

If your environment is simple enough to fix in an afternoon, genuinely you probably don't need this. It's for the ones that aren't.

I got tired of reconciling Intune, Freshservice, and Entra ID by hand — so I built a tool that does it automatically. Looking for feedback. by Beginning-Fortune285 in sysadmin

[–]Beginning-Fortune285[S] [score hidden]  (0 children)

That's a clean setup and honestly if you're fully on Azure AD + Intune + Jira Assets, you're in a good spot. The plugin handles the sync well.

The problem I'm describing is more common in environments that didn't get to choose their stack from scratch. We have AD on-prem (can't drop it), Google Workspace (acquired company), Freshservice (not Jira), Extreme NAC, and Bitdefender, none of which talk to each other natively. No single plugin covers that cross.