Connect to all Office 365 Services PowerShell - Supports MFA too

Using our All-in-One PowerShell script, you can connect to all Office 365 Services using a single cmdlet. It supports both MFA and non-MFA account -Exchange Online -Azure AD -SharePoint Online -Skype for Business Online -Security & Compliance Center -Teams

 
 
 
 
 
5 Star
(2)
9,914 times
Add to favorites
Office 365
10/17/2019
E-mail Twitter del.icio.us Digg Facebook
  • Can i trust the source?
    2 Posts | Last post December 03, 2019
    • Dear all,
      
      some time ago I stumbled upon this script. It is nice, but I somehow don't trust it. When I got to the website (office365reports.com) some months ago I got virus alerts and javascript redirections to virus sites. It was definately a problem of the site, not on my client.
      Also I think it is not very serious that there is no information about the authors on the website.
      
      I'd like to use the script but don't trust it anymore, I give my credentials in there so it might be also dangerous. Maybe some feedback of the authors would be nice.
      
      Kind regards,
      Jonathan
    • Hi Jonny_Blue,
      
      I am the publisher of the script. This is a PowerShell script, so you shall take a look at the code easily.The passed credentials are directly submitted to Office 365. If you have any feedback for improvements in the script, then I am happy to hear that. The script is used by many Office 365 experts. 
      Our site is O365Reports.com not the one you mentioned. 
      
  • No question, just Kudos - Thank you for this
    1 Posts | Last post November 02, 2019
    • Thank you for this script.  It's a huge time saver.
  • Error on MFA connection to EO
    3 Posts | Last post October 11, 2019
    • It says its check AzureAD, prompts me for all my MFA credentials, then I get the checking connection to ExchangeOnline then the error.
      
      A parameter cannot be found that matches parameter name 'BypassMailboxAnchoring'.
      At C:\Users\bweir\AppData\Local\Apps\2.0\VTTZQTDR.KQC\6Y75CQM1.7P9\micr..tion_a8eee8aa09b0c4a7_0010.0000_a11671f1a68bb628\CreateExoPSSession.ps1:218 char:231
      + ... essionOption -Credential $Credential -BypassMailboxAnchoring:$BypassM ...
      +                                          ~~~~~~~~~~~~~~~~~~~~~~~~
          + CategoryInfo          : InvalidArgument: (:) [New-ExoPSSession], ParameterBindingException
          + FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.Exchange.Management.ExoPowershellSnapin.NewExoPSSession
    • Hi Brendan,
      I believe you made some changes in the script as we didn't use the "ByPassMailboxAnchoring" switch in the script. Can you share the modified script to analyze the root cause of the issue?
    • That was the stock script I downloaded from TechNet. Today I tried it again, and it seems to be working. I am sure I did something wrong in vscode ... 
  • Support for Intune Graph API
    1 Posts | Last post October 09, 2019
    • Support for Intune Graph API would be a really nice feature, since those are often used together. Any plans for this ?? 
  • Extension to capability for non-commercial O365 clouds
    2 Posts | Last post October 09, 2019
    • Any value in adding an '-Environment' parameter to this script to support connecting to non-commercial O365 endpoints such as Gov, Fed, and GCC environments?
    • Hi Illacasella,
      As of now, this script doesn't support -Environment variable. We will update you once it is available.