Support

Please refer to our documentation found here or contact to support at support@senserva.com or +1 651 728 6108

SenservaPro wants users to work with fresh data, so no database is used. Results are cached at the server for about an hour after a scan. Note that the web client can hold result data for a longer time and data can be exported from the web client.

As many as you want. However, please note that we only allow one scan at a time to make sure we do not bother Azure! A scan request is has a “first in, first out” queue. Users will be able to complete their scan in the order that it was received.

As many as you want. SenservaPro works with your Azure environment and can run a scan on all tenants without increasing your spend.

From the left navigation menu in your Azure applications. click ‘Azure Active Directory’ –> ‘Properties’ on the bottom of the screen ensure that ‘Access management for Azure resources’ button is toggled to ‘Yes’.

Absolutely! Regardless of how you are using Microsoft products, they use the same security back-end and Senserva helps to make that security better.

To fully scan a user should should be a ‘Global Reader’ and log into the installed Senserva application in their tenant. When available, it would be Senserva’s recommendation to use Privileged Identity Management (PIM) to enable this role while scanning.

We have tested and support the Chrome, Firefox, and Edge(v83+) browsers.

Senserva scans at the rate of approximately 5,000 users per hour.

Senserva saves the results for 40 hours after a scan. If you start a new scan, the past scan data is deleted.

The only user who can see the results of a scan is the user that performed the scan, unless that user exports the data via the SenservaPro user interface.

Our basic install in Azure is a size S1 Azure Web Application. This can be scaled as necessary based on your data and organization size.

We use a detail weighting system based on current configurations and activities of users. Please contact us for details

The way that Azure logs the event data around these shared mailboxes gives a time and date stamp for the account that access the shared mailbox and not the shared mailbox itself.