Crates

Pulling logs from O365, identifying and rectifying malicious mail flow rules. Grabbing forensic data from cloud & end-user devices

Customer would like an "uninstall crate" button. Desired functionality would allow them to quickly delete all elements unpacked as part of a crate. This is especially important when crates are replaced with new versions. They suggested a wizard that allows the user to view and select all elements of a crate, with a "used in x number of crates" indicator so they could deselect shared sub workflows, and then click "delete all selected."

I’d love for OneDrive access delegation to be added to the offboarding workflow.

Automatically document all Sharepoint site URLs in ITGlue/Hudu/etc

It seems that for the reporting portions of the workflow there is no error handling. That is, if the app activity report fails to run for any reason the workflow stops and is considered a failure. it would be an improvement to have the workflow report that that specific function failed but proceed to the rest of the compromised workflow as the reporting isnt necessarily the most important step in this procedure and its important the other steps are still ran!

The final ticket update currently only has the note: "User Creation Process for <user> has been completed. Note that any additional actions will now be performed that are actioned by a workflow listener, such as documentation.". It is missing the logging of the results of the tasks, like in the old crate and even in the Microsoft: User Offboarding crate.

A form to grant accesses outside of usual working country. Give options for country or countries of travel & return date to the US. Option for a cruise generator as that might have multiple countries / different limitations. Most important piece would be the aspect of the return date and removing the employees exceptions.

Description: We have deployed the crate "Assign asset/config to ticket based on contact", which works well in environments integrated with on-prem Active Directory (AD). However, it appears that this functionality does not currently work with Azure Active Directory (AzureAD). Issue: The crate seems to rely on contact-to-asset/config relationships that are populated via on-prem AD integrations. In environments using AzureAD exclusively (without hybrid AD), these mappings are either unavailable or not functioning as expected. As a result, assets/configs are not automatically assigned to tickets based on the contact when using AzureAD. Request: Please consider adding support for AzureAD in this crate, either through: Direct integration with AzureAD user/contact attributes, Or by providing a method to map contacts to assets/configs in AzureAD-only environments.

Currently the Country/Region setting of the onboarding user setup copies the usage_location e.g. GB, so we essentially get Country = GB and usage Location=GB. What I would like is for this to be split out like the City, Street etc and get the country value from PSA, rather than copying the usage location. Would also be great if there was some logic added to get this country from PSA and set the usage location e.g. GB, US, AU etc automatically based off this country name from PSA. This would allow customers with multiple regional offices have the correct seeting in the MS User properties set per the site the PSA contact is under. (We use Connectwise, it may be more difficult for other PSA's though) Where the ticket is logged by a PSA contact uder the company (i.e. completed by a customer) the created ticket should also use that contact on the created ticket. So whoever fills the form is then the ticket contact automatically, as long as they exist under that company as a contact in PSA

Could we add a SIP:<primary email> by default because if this is not there it will gives issues with federated users. Also would be nice to add other proxy addresses in the form for an alias for example.