Security teams ask the same questions before approving any app. This page answers them and lists every permission Sprawlsight asks for. Access: ongoing access is read-only. Setup creates Sprawlsight's enterprise apps and assigns read-only roles; it never changes a setting, and nothing it asks for opens mailboxes, files or chats. Data: results are stored in Microsoft Azure (Canada Central), and names can be masked in reports; the privacy notice lists what leaves that region, such as the emails Sprawlsight sends, and what's deleted on request. Control: delete Sprawlsight's apps in Microsoft Entra ID > Enterprise applications, and its access ends. The permissions are approved in Microsoft Entra ID like any enterprise app, and removable there. The page lists each app, what it enables, every Microsoft Graph and API permission with the reason it's needed, and the read-only roles an admin assigns in one step: setup uses that admin's own sign-in, once, and puts Azure Reader on every subscription the admin can manage if Azure is included. That sign-in's tokens are used straight away and never stored. The Setup app's delegated permissions are listed too (RoleManagement.ReadWrite.Directory for Microsoft Graph, user_impersonation for Azure Service Management and Authorization.RoleAssignments.Write for the Power Platform API): they act only as that admin, to assign the read-only roles, and the Setup app can be deleted once setup is done.