![]() ![]() If you are using PowerShell 7 on Windows, you need version 2.0.4 or later of the EXO V2 module to connect to Exchange Online Powershell. But in this situation, it could be that the cmdlet does not have a REST call (yet). The Exchange Online PowerShell V2 module (referred to as EXO V2 module) is supported in Windows PowerShell 5.1. Often they find that the Set/New cmdlet is unavailable, while the Get is available, e.g.īefore, this could be an indication those commands were removed from the role assigned to you, such as the New-MailboxImportRequest cmdlet which only is available if you have mailbox import/export assigned. The confusion usually starts when people enter commands or run scripts, and find cmdlets are “missing”. Your exact number might vary, based on the roles assigned to your account. ((Get-Module).Where | Select-Object -ExpandProperty ExportedCommands).GetEnumerator() | Measure-ObjectĪs you can see above, after connecting this version supports 397 cmdlets for my role in addition to the 31 available pre-connecting. Connect-ExchangeOnline -UserPrincipalName ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |