Let me just drift around this corner

Hey CIPP Family, are you ready to get a little bit faster with deploying your standards at your clients, making them less furious? This release is one for you. After our latest tenant alignment updates our Discord started revving with excitement.

This version is called the Tokyo Drift, because that's what you asked for; better drift management that we can extend on in the future. And of course we delivered on this feature, because that's what family does. (These Fast & Furious puns are even annoying me, no worries)

Vroom Vroom, Drift management is here

So CIPP has always had its standards - Standards allow you to deploy your preferred settings to a tenant easily and create a baseline, but some of you wanted a bit more; you want to be alerted on every detail that is outside of your preferred configuration and have the ability to restore the config you want, or you want to remove the policies that have been added on accident. That's now possible with the new drift management.

Enabling a Drift Template allows you to receive emails or webhooks that you can setup per template, and you can approve, accept as a customer deviation, or deny easily using the management portal.

Now let me explain that a little more; when you setup a Drift Template, we start monitoring the environment if everything that you put in that Template has been deployed and is in the state that you want it. During setup of the template you have a choice; do you want to auto remediate this issue, or not.

If you select not to remediate, it'll generate a deviation error and let you know. It'll just report. You then have the choice to set it up correctly with a one-off job, until it deviates again.

I hear you I hear you. "How do I explore this? how do I play with it?!" well, the documentation has been updated, but even cooler, try our new demos!

Creating a Drift Template

Managing a Drift Template

Audit Logging has been pimped

So the biggest issue with Microsoft's audit logs is the many formats they use; Exchange logging puts usernames in weird places or adds underscores, an Entra audit log can have the users GUID, username, or primary email address as the username, but all in slightly different situation

So, we improved that, we now enrich the data in the audit logs with "CIPP" versions of them, for example "CIPPUsername" is 100% guaranteed to actually be the username, and not a random signifier. We didn't stop there. Why do that when you can expand what you have available. We added the ability to not just create audit log searches, but you can zoom in on each log entry, getting all the CIPP enhanced interace. No more messing with CSV or JSON files from the audit api.

Also, we made sure that for the log entries we also pull in the correct users when they come from your partner tenant. No more User_longguid, but immediately seeing edits made.

Of course we made a demo for you, check that one out here.

Want to see on how you setup alerting? Check that one out over here.

Making History

Another cool feature that we've built is tracking the history for tenants. We've always had the logbook, but those are a little hard to read, so we improved the filtering, and now generate a timeline of every single event CIPP had on a tenant inside of the standards management. That easily allows you to see what change was made and when.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

v8.3.0 - Tokyo Drift

Let me just drift around this corner

Vroom Vroom, Drift management is here

Audit Logging has been pimped

Making History

Sponsors

What's Changed

New Contributors

Contributors

Uh oh!