• Need to query for personal site and its properties with a user email address or UPN.
• Option to query for all Onedrive Sites on a tenant and its properties
• The tenant-level settings override any settings at the site collection level. Collect Tenant Level External Sharing settings and limit the User level with same or more restrictive than the Tenant level

• Microsoft Graph (preferred)
• SharePoint CSOM
• SharePoint REST API

$Result = @()
$DLList = Get-DistributionGroup -RecipientTypeDetails MailUniversalSecuritygroup -resultsize unlimited|Select Alias,name,PrimaryEmailAddress
foreach($DL in $DLList)
{
     $DLPerm = Get-ADPermission -Identity $DL.Name | where {($_.ExtendedRights -like "*Send-As*") -and ($_.IsInherited -eq $false) -and -not ($_.User -like "NT AUTHORITY\SELF")}|Select Identity,User
     $Result += $DLPerm

$Result|select Identity,User|Export-Csv SendAs_report.csv -NoTypeInformation 

Start-Transcript -Path C:\temp\DLSend-asPerms.txt
Import-Module ActiveDirectory
Set-Location AD:
$MailDLs = Get-ADObject -Filter "(objectClass -eq 'group') -and (proxyAddresses -like '*')" -SearchScope Subtree -ResultPageSize 200000
Write-Host "Total $($MailDLs.Count) MailDLs found"

$i = 0

foreach($MailDL in $MailDLs){
     $i++
     $SendasEntries = $NULL
     Write-Progress -Status "Processing $i / $($MailDLs.Count)" -PercentComplete ($i / @($MailDLs).Count) * 100
     $SendasEntries = Get-ACL $MailDL.DistinguishedName | select -ExpandProperty Access | ?{($_.ActiveDirectoryRights -eq "ExtendedRight") -and ($_.objectType -eq "ab721a54-1e2f-11d0-9819-00aa0040529b") -and          
                      ($_.IsInherited -eq $false) -and $_.IdentityReference -ne "NT AUTHORITY\SELF" }
     if($NULL -eq $SendasEntries){
          Write-Host "DL $($MailDL.Name) - Has no Sendas Entries"
     }
    foreach($SendasEntry in $SendasEntries){
          Write-host "DL $($MailDL.Name) - $($SendasEntry.IdentityReference) has Sendas Perms"
    }
}
Stop-Transcript

The re-written code uses Get-ACL cmdlet to collect the Send-as permissions and for over 100,000 DGs it took a little over 3 hours to generate the report

• This script launches Windows Presentation framework based UI form.
• Provides users with options either to run Online Query or process users from a CSV list.
• Using a License picker window, users can Add and/or Remove licenses.
• Apply it on all users or selected users from the list, all at once.
• This script will only append to or remove the existing user licenses and plans.
• At Present, this script requires no Input parameters, but default switches like -Verbose can be added to view progress on the Powershell window.
• It creates a log by default on the script's directory which includes the Licenses and runtime details.

• Use Get-Messagetrackinglog and/or Get-Messagetrace (if you are in Hybrid, you will need to track both) to collect the recipients details to whom the message was delivered to.
• Use an account that has Impersonation permissions on On-perm and Online if you are in Hybrid, and use it with this script to find the read status of the given Message. Something like below..

• Uses Autodiscover to find the EWS URL, but for increased performance, one can specify the EWSUrl parameter manually.
• Can be used against Office 365 or On-Perm mailbox. If the Email message was sent to Online and On-Perm mailboxes, use an account that has impersonation permissions on both org for easy tracking.
• Searches Inbox first and if the message is not found in the Inbox Folder, then the script searches the entire mailbox.
• Error message is returned on the result object, no separate log file parsing is required to find the complete status

•                Collecting asset information, configuration from all the workstations
•                Collect mailbox statistics or other details for thousands of objects...etc.

1. Easy to use.
2. When used with Cmdlets or Remote PowerShell, it automatically detects and loads the (only) required modules to the sessions.
3. Checks if it can complete the first job without errors before scheduling all the jobs to run in parallel.
4. By default, the script processes the jobs in batches. With batching, the resource consumption is very less and its proportional to the batch size which can be adjusted as required.
5. Ability to pause the Job scheduling in-between batches. This is very useful if too many requests are overloading the destination.
6. Creates a runtime log by default.