Crates

To alert when end clients Sharepoint storage is reaching capacity similar to the mailbox quotas to proactively prevent shut down of Sharepoint sites past capacity.

Crate to alert on upcoming expirations of subscriptions (12 or 36 month) 30 days out.

When you install a crate, if the crate is built to support multiple PSA or RMM integrations that you don't have, the list of workflows is generally very long. In a perfect world, installing a crate would only install the components of the crate that are useful to the partner. Absent that ability, what if there was a way to hide/filter all workflows that meet exclusion criteria defined by the partner.

If cybercns sees insecure protocols & ciphers (old ssl/tls), have a crate that allows you to automatically apply the fix (applies schannel reg keys)

We've come up with below list of enhancements for the AAD to CWM sync workflow based on testing multiple scenarios. In its current state, we've found that: Rewst only syncs name/email/job title/mobile phone Rewst does not sync office phone If data is missing on the CWM contact (mobile/job title/etc) the Rewst sync will populate that data If data is present on CWM contact but different on the M365 user object, the Rewst sync will not overwrite that data If data is removed from the CWM contact, the Rewst sync will re-populate that data If a disabled/blocked sign-in M365 user is re-enabled, the Rewst sync won't re-activate the CWM contact and doesn't update blank fields Our desired state would be: Rewst syncs name/email/job title/office phone/mobile phone Rewst inactivates CWM contacts that have been deleted from M365 unless the CWM contact is flagged using a custom field in CWM (or similar exclusion method). This solves the conflict between needing to keep some CWM-only contacts while having clients whose standard is to delete rather than disable users. Rewst re-activates inactive CWM contacts that are enabled, re-enabled, or recreated after being deleted in M365. This solves an issue where someone could manually inactivate a CWM contact for an enabled M365 user. This also solves an issue where a deleted M365 user is recreated after a rehire or similar situation. Rewst overwrites CWM contact data if a field contains data in both in M365 and CWM, but won't overwrite CWM contact data if a field contains data in CWM only. This solves the conflict where if we populate a mobile phone number on the CWM contact but not on M365 user, the sync won't blank out the data on the CWM contact. While we want to use M365 as the source-of-truth, most of our clients don't want their user's mobile phone numbers visible in the GAL.

I think some kind of desired state workflow would be a game changer for me. We are achieving parts of this but at the moment to verify everyone and everything is perfect it requires a person to touch a ton of portals and pull and compare data. If Rewst could reach into all the portals and compare data and remediate based on what should be parameters. Endpoints - Compare everything from AD, Azure AD, RMM, PSA, huntress, EDR, MTR, AV, insert tool here. User - Make sure they are setup in the portals they should be. Spam filtering, AD/Azure AD, signature manager, (depending on reach), creative cloud, (whatever tools they should have deployed to them) Client - What portals should they be in. Did we stupidly forget to deploy spam filtering for 5 months (totally didn't happen.....) Are our standards applied to the clients 365/endpoints/users/ help me out with idea's here. My overarching idea on this is a base workflow that figures some of this out automatically based on existing integrations. But then the crate marketplace has 50-100 whatever mini crates that do one thing and you can build your own version of this. Also have a space to tie in API/Scripts that aren't yet rewst supported. So the account management part of this would be pretty awesome because if I could then take all the desired states and flow it over to lifecycle insights(or insert some other less good QBR tool here) this would show we are doing what we say we are.

In the ITGlue crate: Document User Details V2, add the ability to exclude specific clients. If the workflow fails because a client is too big, I want to be able to have the workflow skip this client and proceed.

currently the crate accounts for cloud only or hybrid, but not for on-prem only.