Frequently Asked Questions
Common questions and answers
Last updated
Common questions and answers
Last updated
Please see our
Entra ID
The plays a vital role during the installation of the Bsure Datacollector. You will require a highly privileged user account due to the . Although the may also be used, we've skipped that in the prior steps. This decision was influenced by the familiarity of most customers with the Global Administrator Role
Azure Subscription
When installing the Bsure Datacollector, the Azure Resource Manager has to assign permissions to certain identities. The task of assigning permissions within an Azure Subscription is reserved for the . Additionally, access to the actual resources within the subscription is required, rendering the insufficient for this purpose
Bsure Insights show users last successful sign-in date in Entra ID. Our app does not have information about when users last logged on to your on-premises Active Directory.
Hybrid customers may have users synced to Entra ID, showing as inactive in Bsure Insights, because they have not signed in to any Microsoft cloud resources recently. But they can still be active in your local AD.
To bring the last logon information from AD in to Bsure Insights, you have to add this information to a user attribute that is being synced to Entra ID.
Our recommended approach:
Run a PowerShell script against your local AD to write Last Logon date to an unused Extension Attribute.
Schedule the script to run daily, using Task Scheduler or an automation tool of your choice.
Script example:
You have to adapt this script to your local environment. Change the OU path, and change extensionattribute2 to the extension attribute you choose.
Navigate to "All Applications" and find the application you installed. The name of the application will be the same as the one you selected during the installation process. Click on the application name to access the Managed Application.
Click on the "Delete" button and confirm your action to initiate the deletion process.
In Entra ID you will see date and time for "Last interactive sign-in" and "Last non-interactive sign-in":
These dates represent the latest sign-in attempt regardless if it was successful or not. An unsuccessful user sign-in from a browser in e.g. a conditional access blocked country would update the "Last interactive sign-in" on that specific user, ref
It is not possible to provide a "last sign-in" date for users not signed in since then, and in Bsure Insights reports they will be stamped as never signed in with "last sign-in" = 01.01.1970, since we simply don't know when or if they ever signed in successfully.
Bsure Insights data collector store the latest successful unique sign-in, unique combination of appId, location_countryOrRegion and userid. It also stores when sign-in event happened, and resourcename, resourceid, applicationname and sign-in type (interactive or non-interactive) related to that unique sign-in event.
Meaning we only store the latest successful sign-in a specific user made to a specific app from a specific country.
NB! LastLogonTimestamp in ActiveDirectory may have up to 14 days delay. Read more about the difference between LastLogon, LastLogonTimestamp and LastLogonDate in Active Directory .
To find the Managed Application Center, enter "Managed Application Center" into the search bar at the top of the page on . Then, select the "Managed Application Center" option from the search results.
Last sign-in date for users is defined as the date of the user's most recent successful interactive or non-interactive sign-in. It is the property from Entra ID.
In Bsure Insights we set January 1. 1970 as sign-in date if Microsoft graph returns a blank value for the property .
According to Microsoft they started populating this field December 1. 2023, but it seems like was populated from .