%3CLINGO-SUB%20id%3D%22lingo-sub-1209567%22%20slang%3D%22en-US%22%3ERe%3A%20Faster%20and%20more%20reliable%20Exchange%20Online%20Management%20using%20PowerShell%20V2%20Cmdlets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1209567%22%20slang%3D%22en-US%22%3E%3CP%3EPowerShell%207%20is%20now%20out%2C%20so%20no%20excuse%20not%20to%20support%20it%20%3A)%3C%2Fimg%3E%20And%20yeah%2C%20automation!%20Keep%20up%20the%20good%20work%2C%20I%20like%20this%20monthly%20release%20cadence.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1210817%22%20slang%3D%22en-US%22%3ERe%3A%20Faster%20and%20more%20reliable%20Exchange%20Online%20Management%20using%20PowerShell%20V2%20Cmdlets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1210817%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F58%22%20target%3D%22_blank%22%3E%40Vasil%20Michev%3C%2FA%3E%26nbsp%3BSupport%20for%20PS%207%2FCore%20in%20an%20active%20work%20in%20progress%20and%20will%20be%20available%20for%20preview%20soon.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1211469%22%20slang%3D%22en-US%22%3ERe%3A%20Faster%20and%20more%20reliable%20Exchange%20Online%20Management%20using%20PowerShell%20V2%20Cmdlets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1211469%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F442608%22%20target%3D%22_blank%22%3E%40navgupta%3C%2FA%3E%26nbsp%3Blooking%20forward%20for%20the%20PowerShell%207%20support%20%3A)%3C%2Fimg%3E%20...%20i'm%20currently%20using%20with%20the%26nbsp%3B%3CSPAN%3E-UseWindowsPowerShell%20switch%20to%20get%20around%20the%20limitation%20today%2C%20although%20it%20still%20doesnt%20import%20the%20older%20cmdlets%20Get-Mailbox%20etc.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3Ea%20question%20around%20the%20v2%20module%20though%2C%20when%20will%20we%20be%20able%20to%20use%20Get-EXORecipient%20-Filter%20against%20the%20company%20value%20...%20today%20i%20have%20a%20lot%20of%20scripts%20which%20use%20Get-Recipient%20-Filter%20%7BCompany%20-EQ%20'XXX'%7D%20but%20this%20doesnt%20translate%20to%20Get-EXORecipient.%20is%20this%20because%20the%20underlying%20graph%20doesnt%20have%20a%20odata%20filter%20for%20the%20Company%20attribute%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1211655%22%20slang%3D%22en-US%22%3ERe%3A%20Faster%20and%20more%20reliable%20Exchange%20Online%20Management%20using%20PowerShell%20V2%20Cmdlets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1211655%22%20slang%3D%22en-US%22%3E%3CP%3EFilter%20is%20absolutely%20critical%20to%20handling%20large%20tenants.%20Not%20only%20to%20allow%20selection%20of%20groups%20of%20users%2C%20but%20is%20used%20in%20conjunction%20with%20a%20%E2%80%9Ctracer%E2%80%9D%20property%20update%20so%20you%20know%20which%20accounts%20have%20been%20processed%20when%20you%20have%20to%20restart%20the%20process%20due%20failures.%26nbsp%3B%3CBR%20%2F%3EEven%20with%20robust%20cloud%20command%2C%20account%20updates%2C%20such%20as%20adjusting%20audit%20settings%2C%20fail%202%2F3rds%20of%20the%20time%20when%20running%20processes%20that%20span%20days%20and%20sometimes%20weeks.%20(At%20least%20with%20about%20165k%20of%20mailboxes)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1211861%22%20slang%3D%22en-US%22%3ERe%3A%20Faster%20and%20more%20reliable%20Exchange%20Online%20Management%20using%20PowerShell%20V2%20Cmdlets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1211861%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20there%20documentation%20on%20how%20this%20new%20module%20connects%20out%20to%20the%20Internet%3F%26nbsp%3B%20I%20installed%20it%20on%20a%20Windows%202016%20server%20where%20we%20have%20tools%20installed%2C%20but%20when%20trying%20to%20connect%20it%20fails%20with%20WinRM%20errors.%26nbsp%3B%20WinRM%20is%20running%20and%20does%20allow%20basic%20auth.%26nbsp%3B%20I%20suspect%20the%20proxy%20that%20outbound%20traffic%20is%20directed%20through%20is%20causing%20issues%20as%20this%20works%20from%20my%20Windows%2010%20laptop%20that%20doesn't%20use%20the%20datacenter%20proxy.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1216141%22%20slang%3D%22en-US%22%3ERe%3A%20Faster%20and%20more%20reliable%20Exchange%20Online%20Management%20using%20PowerShell%20V2%20Cmdlets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1216141%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F575418%22%20target%3D%22_blank%22%3E%40JWare%3C%2FA%3E%26nbsp%3B-%20The%20EXO%20V2%20Module%20uses%20AzureAD%20user%20based%20authentication%20for%20the%20new%20Cmdlets.%20At%20the%20same%20time%2C%20it%20uses%20WinRM%20to%20establish%20remote%20session%20for%20running%20older%20RPS%20Cmdlets.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EPlease%20share%20your%20error%20in%20below%20format%20as%20described%20in%20documentation%20here%20-%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fexops-docs%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2Fexops-docs%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1216147%22%20slang%3D%22en-US%22%3ERe%3A%20Faster%20and%20more%20reliable%20Exchange%20Online%20Management%20using%20PowerShell%20V2%20Cmdlets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1216147%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F388856%22%20target%3D%22_blank%22%3E%40UW_Scott%3C%2FA%3E%26nbsp%3B-%20We%20are%20totally%20aligned%20with%20your%20thought%20here.%20Server%20side%20filters%20will%20be%20available%20in%20upcoming%20releases%20of%20the%20module.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHowever%2C%20you%20can%20always%20use%20filters%20on%20client%20side%20using%20'Where-Object%22%20as%20the%20new%20Cmdlets%20retrieve%20data%20significantly%20faster%20than%20their%20RPS%20counterparts.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1216150%22%20slang%3D%22en-US%22%3ERe%3A%20Faster%20and%20more%20reliable%20Exchange%20Online%20Management%20using%20PowerShell%20V2%20Cmdlets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1216150%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F55238%22%20target%3D%22_blank%22%3E%40Jamie%20BRANDWOOD%3C%2FA%3E%26nbsp%3B-%20You%20guessed%20it%20right.%20A%20lot%20of%20filterable%20properties%20are%20not%20available%20in%20odata%20thus%20making%20it%20harder%20to%20support%20filters%20on%20those.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESince%2C%20Get-EXORecipient%20is%20significantly%20faster%20than%20Get-Recipent%2C%20how%20about%20fetching%20the%20company%20value%20property%20for%20all%20recipients%20and%20using%20a%20client%20side%20filtering%20using%20%22Where-Object%22%20clause%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1217181%22%20slang%3D%22en-US%22%3ERe%3A%20Faster%20and%20more%20reliable%20Exchange%20Online%20Management%20using%20PowerShell%20V2%20Cmdlets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1217181%22%20slang%3D%22en-US%22%3E%3CP%3ECould%20you%20please%20confirm%20if%20the%20new%20EXO%20V2%20module%20supports%20the%20national%20clouds%2C%20like%26nbsp%3B%3CSPAN%3EOffice%20365%20operated%20by%2021Vianet%20in%20China%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1217189%22%20slang%3D%22en-US%22%3ERe%3A%20Faster%20and%20more%20reliable%20Exchange%20Online%20Management%20using%20PowerShell%20V2%20Cmdlets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1217189%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F575418%22%20target%3D%22_blank%22%3E%40JWare%3C%2FA%3E%26nbsp%3B%3A%20Proxies%20can%20be%20annoying.%3C%2FP%3E%0A%3CP%3EThis%20%3CI%3Eusually%3C%2FI%3E%20helps%20to%26nbsp%3Bresolve%20that%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%24options%20New-PSSessionOption%20-ProxyAccessType%20IEConfig%3CBR%20%2F%3EConnect-ExchangeOnline%20-PSSessionOption%20%24options%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFor%20the%20rest%20calls%2C%20it%20may%20be%20necessary%20to%20set%20up%20the%20default%20proxy%20settings%20for%20the%20.NET%20side%20of%20things%26nbsp%3B%3CEM%3Ebefore%3C%2FEM%3E%20connecting%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%5BSystem.Net.WebRequest%5D%3A%3ADefaultWebProxy%20%3D%20%5BSystem.Net.WebProxy%5D%3A%3Anew('%3CPROXYURL%3E%3A%3CPROXYPORT%3E')%3C%2FPROXYPORT%3E%3C%2FPROXYURL%3E%3C%2FP%3E%0A%3CP%3E%5BSystem.Net.WebRequest%5D%3A%3ADefaultWebProxy.UseDefaultCredentials%20%3D%20%24true%3C%2FP%3E%0A%3CP%3E%5BSystem.Net.WebRequest%5D%3A%3ADefaultWebProxy.BypassProxyOnLocal%20%3D%20%24true%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1222277%22%20slang%3D%22en-US%22%3ERe%3A%20Faster%20and%20more%20reliable%20Exchange%20Online%20Management%20using%20PowerShell%20V2%20Cmdlets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1222277%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%20I've%20reported%20this%20to%20the%20feedback%20email%20address%20as%20well%2C%20but%20the%20-Identity%20parameter%20fixes%20outlined%20in%20this%20post%20-%20seem%20to%20have%20only%20been%20applied%20to%20Get-EXOMailbox.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGet-EXO%3CEVERYTHINGELSE%3E%20still%20can%20only%20accept%20the%20Azure%20AD%20ObjectId%2FUserPrincipalName%2C%20or%20the%20EXO%20ExternalDirectoryObjectId%2FUserPrincipalName.%3C%2FEVERYTHINGELSE%3E%3C%2FP%3E%3CP%3EGet-EXOMailboxFolderPermission%20erroneously%20demands%20that%20a%20backslash%20comes%20after%20the%20colon%20in%20Identity.%26nbsp%3B%20However%2C%20when%20using%20the%20FolderId%2C%20rather%20than%20the%20FolderPath%2C%20the%20backslash%20shouldn't%20be%20there.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1222926%22%20slang%3D%22en-US%22%3ERe%3A%20Faster%20and%20more%20reliable%20Exchange%20Online%20Management%20using%20PowerShell%20V2%20Cmdlets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1222926%22%20slang%3D%22en-US%22%3E%3CP%3ERegarding%20the%20progress%20around%20Prefix%2C%20I%20think%20it%20would%20be%20nice%20to%20also%20have%20CommandName%20and%20FormatTypeName%20available%20as%20well.%26nbsp%3B%20If%20we%20only%20need%20to%20run%201%20or%202%20cmdlets%2C%20it's%20way%20faster%2Fbetter%20to%20only%20download%20those%202%20cmdlets%20(and%20optionally%20their%20format%20type%20data).%26nbsp%3B%20This%20idea%20is%20in%20the%20name%20of%20efficiency%20both%20for%20Microsoft%20and%20the%20customers.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1235027%22%20slang%3D%22en-US%22%3ERe%3A%20Faster%20and%20more%20reliable%20Exchange%20Online%20Management%20using%20PowerShell%20V2%20Cmdlets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1235027%22%20slang%3D%22en-US%22%3E%3CP%3EAny%20movement%20on%20Server%20Side%20filters%20or%20updates%20on%20levels%20of%20available%20filterable%20properties%20with%20an%20OData%20query%20...%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1235082%22%20slang%3D%22en-US%22%3ERe%3A%20Faster%20and%20more%20reliable%20Exchange%20Online%20Management%20using%20PowerShell%20V2%20Cmdlets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1235082%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F55238%22%20target%3D%22_blank%22%3E%40Jamie%20BRANDWOOD%3C%2FA%3E%26nbsp%3B-%20Server%20side%20filters%20are%20a%20work%20in%20progress.%20A%20few%20wild%20card%20operators%20which%20ODATA%20doesn't%20support%20will%20not%20be%20available%20in%20the%20EXO%20cmdlets.%20Rest%20will%20be%20available.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1263197%22%20slang%3D%22en-US%22%3ERe%3A%20Faster%20and%20more%20reliable%20Exchange%20Online%20Management%20using%20PowerShell%20V2%20Cmdlets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1263197%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20loving%20the%20new%20module%20so%20far%2C%20it's%20infinitely%20easier%20to%20script%20the%20install%2C%20maintenance%2C%20and%20connection%2C%20and%20I%20can't%20wait%20for%20cert%20based%20auth.%3C%2FP%3E%3CP%3EHowever%2C%20what%20is%20the%20plan%20for%20Exchange%20Online%20Protection%3F%20It%20was%20included%20in%20the%20V1%20module%2C%20so%20are%20it's%20commands%20going%20to%20be%20made%20available%20in%20the%20V2%20module%20as%20well%2C%20or%20is%20there%20another%20module%20in%20the%20works%20specifically%20for%20it%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1263827%22%20slang%3D%22en-US%22%3ERe%3A%20Faster%20and%20more%20reliable%20Exchange%20Online%20Management%20using%20PowerShell%20V2%20Cmdlets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1263827%22%20slang%3D%22en-US%22%3E%3CP%3EExchange%20Online%20Protection%20cmdlets%20are%20available%20in%20the%20latest%20version%20of%20EXO%20PowerShell%20V2%20module%20published%20on%2030th%20March.%3C%2FP%3E%0A%3CP%3ECheck%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fexops-v2%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2Fexops-v2%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1264676%22%20slang%3D%22en-US%22%3ERe%3A%20Faster%20and%20more%20reliable%20Exchange%20Online%20Management%20using%20PowerShell%20V2%20Cmdlets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1264676%22%20slang%3D%22en-US%22%3E%3CP%3EGreat%20timing!%20I%20just%20updated%20and%20everything%20seems%20to%20be%20working%20well%20so%20far.%20Cheers!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1269625%22%20slang%3D%22en-US%22%3ERe%3A%20Faster%20and%20more%20reliable%20Exchange%20Online%20Management%20using%20PowerShell%20V2%20Cmdlets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1269625%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20awesome.%20We%20have%20few%20automations%20and%20been%20looking%20to%26nbsp%3B%20use%20CBA%20to%20authenticate.%20Is%20there%20any%20TAP%20program%20we%20can%20sign%20up%20for%20to%20help%20validate%20any%20scenarios.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1338553%22%20slang%3D%22en-US%22%3ERe%3A%20Faster%20and%20more%20reliable%20Exchange%20Online%20Management%20using%20PowerShell%20V2%20Cmdlets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1338553%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20a%20script%20in%20which%20I%20need%20to%20get%20the%20FolderPath%20for%20the%20Calender%20folder%20in%20each%20mailbox%2C%20for%20which%20I%20use%26nbsp%3B%3CI%3EGet-MailboxFolderStatistics.%26nbsp%3B%3C%2FI%3ETo%20test%20the%20performance%20I%20measured%20the%20time%20doing%26nbsp%3B%3CI%3EGet-MailboxFolderStatistics%20%3C%2FI%3Eand%26nbsp%3B%3CI%3EGet-EXOMailboxFolderStatistics%26nbsp%3B%3C%2FI%3Efor%20all%20mailboxes.%20With%20the%20new%20and%20supposedly%20faster%20cmdlet%20this%20took%204x%20longer!%26nbsp%3BOnly%20when%20I%20ran%20the%20test%20a%20second%20time%20was%20it%20slightly%20faster%20(like%2025%25)%20than%20the%20old%20cmdlet%2C%20because%20it%20apparently%20uses%20caching.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EIf%20we%20cannot%20assume%20that%20the%20new%20cmdlets%20are%20at%20least%20not%20slower%20than%20the%20old%20ones%2C%20then%20I%20don't%20see%20the%20point%20in%20switching%20to%20them.%20So%20far%20I'm%20not%20impressed.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20also%20noticed%20that%20Get-Help%20-Online%20will%20open%20the%20wrong%20URL%20(it%20uses%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fexchange%2Fexchange-ps-v2-module%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fexchange%2Fexchange-ps-v2-module%2F%3C%2FA%3E%26nbsp%3Bwhen%20it%20should%20be%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fexchange%2Fpowershell-v2-module%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fexchange%2Fpowershell-v2-module%2F%3C%2FA%3E)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1338612%22%20slang%3D%22en-US%22%3ERe%3A%20Faster%20and%20more%20reliable%20Exchange%20Online%20Management%20using%20PowerShell%20V2%20Cmdlets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1338612%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F152324%22%20target%3D%22_blank%22%3E%40Gerard%20van%20der%20Land%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20is%20not%20expected.%20We%20would%20like%20to%20debug%20further%20and%20see%20why%20Get-EXOMailboxFolderStatistics%20is%20slower%20for%20you.%20We%20have%20not%20heard%20any%20feedback%20for%20it's%20slowness.%20Can%20you%20share%20the%20details%20at%20the%20email%20which%20gets%20printed%20when%20you%20do%20Connect-ExchangeOnline%20%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20will%20take%20it%20up%20from%20there%20for%20further%20investigation.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%3C%2FP%3E%0A%3CP%3EExchange%20Online%20IT%20Admin%20Experiences%20Team%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1338753%22%20slang%3D%22en-US%22%3ERe%3A%20Faster%20and%20more%20reliable%20Exchange%20Online%20Management%20using%20PowerShell%20V2%20Cmdlets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1338753%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20can%20we%20expect%20certificate%20based%20auth%20support%3F%20Unfortunately%20we%20have%20lot%20of%20automation%20and%20we%20cannot%20leverage%20this%20module%20until%20CBA%20is%20supported.%3C%2FP%3E%3CP%3EHappy%20to%20help%20with%20any%20testing%20or%20validation.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1339155%22%20slang%3D%22en-US%22%3ERe%3A%20Faster%20and%20more%20reliable%20Exchange%20Online%20Management%20using%20PowerShell%20V2%20Cmdlets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1339155%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F152324%22%20target%3D%22_blank%22%3E%40Gerard%20van%20der%20Land%3C%2FA%3E%26nbsp%3BI%20forget%20where%20it%20is%20documented%20but%20the%20first%20MS%20Graph%20based%20cmdlet%20execution%20is%20known%20to%20take%20a%20while%20as%20it%20sets%20up%20the%20MS%20Graph%20authentication.%26nbsp%3B%20The%20second%20and%20later%20commands%20are%20when%20you%20see%20the%20enhanced%20performance.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhere%20I've%20noticed%20the%20dramatic%20speed%20increase%20is%20with%20large%20large%20sets%20of%20data%20where%20it%20is%20now%20saving%20me%20many%20hours%20of%20script%20processing%20time.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1415011%22%20slang%3D%22en-US%22%3ERe%3A%20Faster%20and%20more%20reliable%20Exchange%20Online%20Management%20using%20PowerShell%20V2%20Cmdlets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1415011%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Exchange%20team%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20Microsoft%20code%20signing%20certificate%20you%20used%20for%20signing%20Exchange%20Online%20PowerShell%20v2%20module%20has%20expired%20on%20May%202nd%202020.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EKind%20regards%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDejan%20Foro%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22mailto%3Adejan.foro%40exchangemaster.ch%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Edejan.foro%40exchangemaster.ch%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EExchangemaster%20GmbH%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22http%3A%2F%2Fwww.exchangemaster.ch%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ewww.exchangemaster.ch%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1417304%22%20slang%3D%22en-US%22%3ERe%3A%20Faster%20and%20more%20reliable%20Exchange%20Online%20Management%20using%20PowerShell%20V2%20Cmdlets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1417304%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20it%20me%20only%2C%20who%20need%20%22get-mailuser%22%20and%20all%20related%20cmdlet%2C%20but%20is%20unable%20to%20find%20them%20from%20new%20module%20(0.4578.0)%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEdit%3A%26nbsp%3B%3CIMG%20class%3D%22lia-deferred-image%20lia-image-emoji%22%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Fhtml%2Fimages%2Femoticons%2Fflushed_40x40.gif%22%20alt%3D%22%3Aflushed%3A%22%20title%3D%22%3Aflushed%3A%22%20%2F%3E%3C%2FP%3E%3CP%3EWorking%20again.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1198604%22%20slang%3D%22en-US%22%3EFaster%20and%20more%20reliable%20Exchange%20Online%20Management%20using%20PowerShell%20V2%20Cmdlets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1198604%22%20slang%3D%22en-US%22%3E%3CP%20class%3D%22note%22%3EFor%20more%20updates%20on%20this%20module%2C%20please%20see%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fexchange-team-blog%2Fannouncing-general-availability-of-the-exchange-online%2Fba-p%2F1436623%22%20target%3D%22_self%22%3EAnnouncing%20General%20Availability%20of%20the%20Exchange%20Online%20PowerShell%20v2%20Cmdlets%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3EAt%20Microsoft%20Ignite%202019%2C%20we%20announced%20-ERR%3AREF-NOT-FOUND-new%20Exchange%20Online%20management%20cmdlets%20and%20showed%20how%20they%20can%20be%20used%20to%20perform%20fast%20and%20highly%20reliable%20data%20retrieval%20%26nbsp%3Boperations.%20These%20cmdlets%20are%20generally%204-8%20times%20faster%20and%20have%20proven%20to%20be%20highly%20reliable%20for%20bulk-retrieval%20scenarios.%20We%20have%20seen%20more%20than%2050%2C000%20total%20downloads%20of%20the%20V2%20module%20available%20via%20-ERR%3AREF-NOT-FOUND-PowerShellGallery%20and%20have%20seen%20around%2011%20million%20V2%20cmdlets%20being%20executed%20in%20the%20past%2030%20days.%20Many%20large%20enterprises%20have%20already%20started%20using%20the%20new%20cmdlets%20in%20their%20production%20environment%20and%20we%E2%80%99re%20very%20proud%20of%20that.%3C%2FP%3E%0A%3CP%3EThe%20new%20EXO%20V2%20module%20contains%20all%20the%20old%20Remote%20PowerShell%20cmdlets%20as%20well%20as%20(currently)%209%20new%20V2%20cmdlets.%20These%209%20cmdlets%20use%20REST%20API%20to%20fetch%20data.%20This%20change%20alone%20makes%20them%20faster%20and%20highly%20reliable.%3C%2FP%3E%0A%3CP%3ESince%20the%20new%20module%20is%20available%20on%20PowerShellGallery%2C%20it%20can%20be%20easily%20installed%20using%20the%20command%20line.%20Compared%20to%20the%20MFA%20PowerShell%20module%2C%20which%20required%20a%20Click-2-run%20installation%2C%20the%20new%20module%20is%20far%20better%20suited%20to%20automation%20scenarios.%3C%2FP%3E%0A%3CP%3EThe%20module%20is%20currently%20in%20Public%20Preview%20and%20will%20be%20released%20as%20%E2%80%9CGenerally%20Available%E2%80%9D%20soon.%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId-1110447009%22%20id%3D%22toc-hId-1110447009%22%20id%3D%22toc-hId-1110447009%22%3E%3CFONT%20size%3D%226%22%3EWhat%E2%80%99s%20new%20post%20Ignite%3F%3C%2FFONT%3E%3C%2FH3%3E%0A%3CH4%20id%3D%22toc-hId-1801008483%22%20id%3D%22toc-hId-1801008483%22%20id%3D%22toc-hId-1801008483%22%3E%3CFONT%20size%3D%225%22%3ESupport%20for%20managing%20customer%20tenants%20using%20Delegated%20Authentication%3C%2FFONT%3E%3C%2FH4%3E%0A%3CP%3EThe%20new%20module%20also%20supports%20CSP%20delegation%20for%20DAP%20(Delegated%20Admin%20Privileges)%20partners.%20Delegate%20admins%20can%20manage%20customer%20tenants%20by%20passing%20their%20customer%20tenant%20ID%20during%20Connect-ExchangeOnline%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%20class%3D%22lia-code-sample%20language-markup%22%3E%3CCODE%3E%24cred%20%3D%20Get-Credential%0A%24customerTenant%20%3D%20%E2%80%9Ccontoso-electronics.onmicrosoft.com%E2%80%9D%0AConnect-ExchangeOnline%20-DelegatedOrganization%20%24customerTenant%20-Credential%20%24cred%3C%2FCODE%3E%3C%2FPRE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ERead%20more%20on%20how%20to%20use%20it%20in%20MFA%20PowerShell%20module%20-ERR%3AREF-NOT-FOUND-here%3C%2FP%3E%0A%3CH4%20id%3D%22toc-hId--6445980%22%20id%3D%22toc-hId--6445980%22%20id%3D%22toc-hId--6445980%22%3E%3CFONT%20size%3D%225%22%3EIdentity%20is%20now%20a%20positional%20parameter%20and%20it%20supports%20name%2Falias%3C%2FFONT%3E%3C%2FH4%3E%0A%3CP%3EThe%20initial%20release%20of%20V2%20module%20didn%E2%80%99t%20support%20using%20name%20and%20alias%20as%20Identity%20parameter.%20This%20was%20a%20conscious%20call%20to%20provide%20better%20performance%20of%20cmdlets%20as%20resolution%20of%20name%20and%20alias%20was%20a%20costly%20operation.%20However%2C%20with%20the%20constant%20feedback%20from%20preview%20community%2C%20we%20learnt%20that%20a%20lot%20of%20scenarios%20require%20quick%20data%20access%20for%20a%20small%20set%20(most%20commonly%201)%20of%20mailbox%20using%20PowerShell%20interactively.%20And%20in%20those%20scenarios%20having%20support%20for%20positional%20parameter%20and%20using%20name%20alias%20brings%20a%20lot%20of%20convenience.%3C%2FP%3E%0A%3CP%3EFor%20example%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%20class%3D%22lia-code-sample%20language-markup%22%3E%3CCODE%3EGet-ExoMailbox%20-Identity%20contosoadmin%40fabrikam.com%3C%2FCODE%3E%3C%2FPRE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%E2%80%A6can%20now%20be%20written%20as%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%20class%3D%22lia-code-sample%20language-markup%22%3E%3CCODE%3EGet-ExoMailbox%20contosoadmin%3C%2FCODE%3E%3C%2FPRE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20data-unlink%3D%22true%22%3EAssuming%20contosoadmin%20is%20the%20alias%20of%20user%20contosoadmin%40fabrikam.com%20of%20course.%3C%2FP%3E%0A%3CH4%20id%3D%22toc-hId--1813900443%22%20id%3D%22toc-hId--1813900443%22%20id%3D%22toc-hId--1813900443%22%3E%3CFONT%20size%3D%225%22%3EImproved%20error%20handling%2C%20reduced%20data%20type%20differences%20and%20many%20more%20bug%20fixes%3C%2FFONT%3E%3C%2FH4%3E%0A%3CP%3EThe%20latest%20version%20of%20client%20module%20contains%20bug%20fixes%20across%20Get-Help%2C%20unwanted%20session%20kills%2C%20almost%20all%20the%20properties%20have%20same%20data-type%20across%20RPS%20and%20V2%20cmdlets%20thus%20reducing%20script%20migration%20overhead.%20Also%2C%20the%20dateTime%20property%20now%20honors%20the%20client-side%20locale%20and%20shows%20time%20according%20to%20your%20local%20machine%20time%20zone.%3C%2FP%3E%0A%3CP%3EPlease%20read%20the%20detailed%20release%20notes%20-ERR%3AREF-NOT-FOUND-here%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId--1824403547%22%20id%3D%22toc-hId--1824403547%22%20id%3D%22toc-hId--1824403547%22%3E%3CFONT%20size%3D%226%22%3EHow%20do%20you%20get%20the%20best%20out%20of%20V2%20cmdlets%3F%3C%2FFONT%3E%3C%2FH3%3E%0A%3CH4%20id%3D%22toc-hId--1133842073%22%20id%3D%22toc-hId--1133842073%22%20id%3D%22toc-hId--1133842073%22%3E%3CFONT%20size%3D%225%22%3EUse%20PropertySets%20and%20Properties%20parameters%3C%2FFONT%3E%3C%2FH4%3E%0A%3CP%3ETraditionally%2C%20RPS%20Cmdlets%20returned%20all%20mailbox%20properties%20in%20the%20output%20object.%20Most%20of%20these%20properties%20were%20not%20usually%20required%20but%20were%20part%20of%20the%20returned%20object%20which%20caused%20performance%20degradation.%20%3CBR%20%2F%3EIn%20the%20new%20module%20we%20have%20bucketized%20certain%20related%20set%20of%20properties%20and%20called%20them%20%E2%80%9CPropertySets%E2%80%9D.%20These%20PropertySets%20are%20simply%20buckets%20of%202%20of%20more%20Properties.%20We%20have%20exposed%202%20new%20parameters%20in%20EXO%20Cmdlets%3A%20Properties%20and%20PropertySets.%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EPropertySets%20%E2%80%93%20it%20accepts%20one%20or%20more%20(in%20comma%20separated%20form)%20names%20of%20the%20properties%20buckets%20i.e.%20PropertySets.%20The%20following%20example%20will%20return%20all%20the%20properties%20mentioned%20in%20Minimum%2C%20Archive%20%26amp%3B%20Custom%3A%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%20class%3D%22lia-code-sample%20language-markup%22%3E%3CCODE%3EGet-ExoMailbox%20-PropertySets%20Archive%2C%20Custom%3C%2FCODE%3E%3C%2FPRE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EProperties%20%E2%80%93%20it%20accepts%20one%20or%20more%20(in%20comma%20separated%20form)%20name%20of%20the%20output%20property%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%20class%3D%22lia-code-sample%20language-markup%22%3E%3CCODE%3EGet-ExoMailbox%20-Properties%20LitigationHoldEnabled%2C%20AuditEnabled%3C%2FCODE%3E%3C%2FPRE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou%20can%20specify%20PropertySets%20as%20well%20as%20Properties%20at%20the%20same%20time%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%20class%3D%22lia-code-sample%20language-markup%22%3E%3CCODE%3EGet-ExoMailbox%20-Properties%20IsMailboxEnabled%2C%20SamAccountName%20-PropertySets%20Delivery%0AGet-ExoCASMailbox%20-Properties%20EwsEnabled%2C%20MAPIBlockOutlookNonCachedMode%20-PropertySets%20ActiveSync%20%0A%3C%2FCODE%3E%3C%2FPRE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20have%20also%20introduced%20a%20new%20concept%20call%20%E2%80%9CMinset%E2%80%9D%20which%20is%20a%20bare%20minimum%20set%20of%20properties.%20If%20you%20don%E2%80%99t%20specify%20any%20PropertySets%2C%20you%20will%20get%20the%20bare%20minimum%20properties%20every%20time.%20If%20you%20specify%20a%20PropertySet%20while%20invoking%20a%20cmdlet%2C%20you%20will%20only%20get%20the%20%E2%80%9CProperties%E2%80%9D%20specified%20in%20the%20PropertySets%20parameter%20and%20you%20won%E2%80%99t%20get%20the%20properties%20listed%20in%20%E2%80%9CMinimum%E2%80%9D%20bucket.%3C%2FP%3E%0A%3CP%3ERead%20more%20about%20property%20sets%20-ERR%3AREF-NOT-FOUND-here.%3C%2FP%3E%0A%3CH4%20id%3D%22toc-hId-1353670760%22%20id%3D%22toc-hId-1353670760%22%20id%3D%22toc-hId-1353670760%22%3E%3CFONT%20size%3D%225%22%3EUse%20Piping%20to%20get%20multi-threading%20benefit%3C%2FFONT%3E%3C%2FH4%3E%0A%3CP%3EPipelines%20act%20like%20a%20series%20of%20connected%20segments%20of%20pipe.%20Items%20moving%20along%20the%20pipeline%20pass%20through%20each%20segment.%20%26nbsp%3BThe%20V2%20module%20invokes%20multiple%20threads%20on%20the%20client%20machine%20to%20parallelize%20execution%20and%20retrieval%20and%20thus%20provides%20a%20better%20performance%20in%20data%20retrieval.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22V2%20Cmdlets%201.png%22%20style%3D%22width%3A%20975px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F173897i63BDC2FBF8299AE6%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22V2%20Cmdlets%201.png%22%20alt%3D%22V2%20Cmdlets%201.png%22%20%2F%3E%3C%2FSPAN%3EIt%20can%20be%20clearly%20seen%20that%20for-looping%20took%20900%20seconds%20to%20get%20Mailbox%20Statistics%20for%20100%20mailboxes%20while%20it%20only%20took%2048%20seconds%20for%20the%20same%20operation%20using%20pipe%20operator.%20Nice!%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId-1343167656%22%20id%3D%22toc-hId-1343167656%22%20id%3D%22toc-hId-1343167656%22%3E%3CFONT%20size%3D%226%22%3EWhat's%20Next%3F%3C%2FFONT%3E%3C%2FH3%3E%0A%3CH4%20id%3D%22toc-hId-2033729130%22%20id%3D%22toc-hId-2033729130%22%20id%3D%22toc-hId-2033729130%22%3E%3CFONT%20size%3D%225%22%3ESupport%20for%20PowerShell%20Core%3C%2FFONT%3E%3C%2FH4%3E%0A%3CP%3EThe%20V2%20module%20works%20only%20on%20Windows%20PowerShell%20version%205.0%20or%20lower.%20It%20doesn%E2%80%99t%20work%20on%20non-Windows%20Operating%20Systems%20i.e.%20Linux%2C%20Mac.%3C%2FP%3E%0A%3CP%3EWe%20plan%20to%20add%20the%20support%20for%20PowerShell%206%20and%207%20in%20the%20new%20V2%20module%20so%20that%20it%20works%20seamlessly%20on%20Linux%2C%20Mac%20and%20windows.%3C%2FP%3E%0A%3CH4%20id%3D%22toc-hId-226274667%22%20id%3D%22toc-hId-226274667%22%20id%3D%22toc-hId-226274667%22%3E%3CFONT%20size%3D%225%22%3ESupport%20for%20Automation%20using%20Certificate%20Based%20Authentication%3C%2FFONT%3E%3C%2FH4%3E%0A%3CP%3EExchange%20Online%20management%20didn%E2%80%99t%20have%20official%20support%20for%20app-only%20scenarios%20i.e.%20background%20jobs%20authentication%2C%20scheduling%20etc.%20Currently%2C%20we%20are%20working%20on%20support%20app-only%20authentication%20using%20Certificates%20and%20Service%20Principal%20objects%20available%20in%20AzureAD.%20This%20is%20really%20important%20work%20and%20will%20help%20get%20you%20off%20Basic%20Authentication%20in%20Exchange%20Online%2C%20which%20as%20we%20hope%20you%20know%2C%20is%20-ERR%3AREF-NOT-FOUND-being%20retired.%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId--479391916%22%20id%3D%22toc-hId--479391916%22%20id%3D%22toc-hId--479391916%22%3E%3CFONT%20size%3D%226%22%3EFrequently%20asked%20questions%3C%2FFONT%3E%3C%2FH3%3E%0A%3CH4%20id%3D%22toc-hId-2137203636%22%20id%3D%22toc-hId-2137203636%22%20id%3D%22toc-hId-2137203636%22%3E%3CFONT%20size%3D%225%22%3EHow%20to%20handle%20the%20Windows%2010%20PowerShellGet%20Error%3F%3C%2FFONT%3E%3C%2FH4%3E%0A%3CP%3EFor%20PowerShell%20version%205.1%20which%20got%20shipped%20with%20Windows%2C%20a%20known%20issue%20causes%20an%20error%20during%20a%20module%20installation%20from%20PowerShell%20Gallery.The%20error%20message%20is%20shown%20below%20and%20the%20installation%20doesn%E2%80%99t%20succeed%20when%20this%20warning%20is%20shown%3A%3C%2FP%3E%0A%3CP%3E%3CFONT%20color%3D%22%23FF0000%22%3E%3CEM%3EWarning%3A%20The%20specified%20module%20%E2%80%98ExchangeOnlineManagement%E2%80%99%20with%20PowerShellGetFormatVersion%20%E2%80%982.0%E2%80%99%20is%20not%20supported%20by%20the%20current%20version%20of%20PowerShellGet.%3C%2FEM%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3EThe%20current%20workaround%20is%20to%20forcefully%20install%20PowerShellGet%20using%20the%20below%20cmdlet%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%20class%3D%22lia-code-sample%20language-markup%22%3E%3CCODE%3EInstall-Module%20PowerShellGet%20-Scope%20AllUsers%20-Repository%20PSGallery%20-Force%20-AllowClobber%3C%2FCODE%3E%3C%2FPRE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou%20will%20then%20need%20to%20re-load%20the%20PowerShell%20session%3B%20you%20can%20do%20this%20with%20the%20command%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%20class%3D%22lia-code-sample%20language-markup%22%3E%3CCODE%3EPowerShell%3C%2FCODE%3E%3C%2FPRE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou%20should%20then%20be%20able%20to%20successfully%20use%20the%20latest%20version%20of%20PowerShellGet%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%20class%3D%22lia-code-sample%20language-markup%22%3E%3CCODE%3EInstall-Module%20-Name%20ExchangeOnlineManagement%20-Verbose%20-Scope%20AllUsers%20-Force%3C%2FCODE%3E%3C%2FPRE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20case%20above%20steps%20doesn%E2%80%99t%20work%20for%20you%2C%20please%20read%20-ERR%3AREF-NOT-FOUND-this%20on%20how%20to%20install%20the%20PowerShellGallery%20module%20manually.%3C%2FP%3E%0A%3CH4%20id%3D%22toc-hId-329749173%22%20id%3D%22toc-hId-329749173%22%20id%3D%22toc-hId-329749173%22%3E%3CFONT%20size%3D%225%22%3EBasic%20Auth%20still%20needs%20to%20be%20enabled%20on%20your%20client%20machine%3C%2FFONT%3E%3C%2FH4%3E%0A%3CP%3EThe%20new%20PowerShell%20V2%20module%20uses%20Modern%20Auth%20to%20establish%20connection%20for%20enabling%20all%20the%209%20(as%20of%20this%20writing)%20REST-based%20V2%20Cmdlets.%20In%20addition%20to%20V2%20cmdlets%2C%20it%20also%20allows%20you%20to%20access%20700%2B%20of%20the%20older%20Remote%20PowerShell%20Cmdlets%20which%20requires%20a%20Remote%20PowerShell%20session%20to%20be%20established.%20Establishing%20an%20RPS%20session%20on%20Windows%20machine%20require%20WinRM%20BasicAuth%20to%20be%20enabled%20on%20the%20client%20machine%20even%20though%20it%20used%20Modern%20Auth%20mechanism%20to%20authenticate.%20The%20WinRM%20Basic%20Auth%20pipeline%20is%20essentially%20used%20for%20transporting%20Modern%20Auth%20tokens.%20If%20WinRM%20Basic%20Auth%20is%20disabled%20on%20the%20client%20machine%2C%20the%20new%20V2%20cmdlets%20will%20continue%20to%20work%20(but%20the%20older%20RPS%20cmdlets%20will%20not)%3C%2FP%3E%0A%3CP%3EWe%20really%20hope%20you%20enjoy%20using%20the%20new%20Exchange%20Online%20V2%20module%2C%20and%20we%20look%20forward%20to%20your%20feedback%20as%20we%20continue%20to%20improve%20them.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22author%22%3EThe%20Exchange%20Admin%20Team%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1198604%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20seen%20more%20than%2050%2C000%20total%20downloads%20of%20the%20V2%20module%20available%20via%20-ERR%3AREF-NOT-FOUND-PowerShellGallery%20and%20have%20seen%20around%2011%20million%20V2%20cmdlets%20being%20executed%20in%20the%20past%2030%20days%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1198604%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdministration%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Eall%20posts%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EScripting%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ETools%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1453940%22%20slang%3D%22en-US%22%3ERe%3A%20Faster%20and%20more%20reliable%20Exchange%20Online%20Management%20using%20PowerShell%20V2%20Cmdlets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1453940%22%20slang%3D%22en-US%22%3E%3CP%3EAny%20news%20on%20the%20PS7%20support%20front%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E

For more updates on this module, please see Announcing General Availability of the Exchange Online PowerShell v2 Cmdlets.

At Microsoft Ignite 2019, we announced new Exchange Online management cmdlets and showed how they can be used to perform fast and highly reliable data retrieval  operations. These cmdlets are generally 4-8 times faster and have proven to be highly reliable for bulk-retrieval scenarios. We have seen more than 50,000 total downloads of the V2 module available via PowerShellGallery and have seen around 11 million V2 cmdlets being executed in the past 30 days. Many large enterprises have already started using the new cmdlets in their production environment and we’re very proud of that.

The new EXO V2 module contains all the old Remote PowerShell cmdlets as well as (currently) 9 new V2 cmdlets. These 9 cmdlets use REST API to fetch data. This change alone makes them faster and highly reliable.

Since the new module is available on PowerShellGallery, it can be easily installed using the command line. Compared to the MFA PowerShell module, which required a Click-2-run installation, the new module is far better suited to automation scenarios.

The module is currently in Public Preview and will be released as “Generally Available” soon.

What’s new post Ignite?

Support for managing customer tenants using Delegated Authentication

The new module also supports CSP delegation for DAP (Delegated Admin Privileges) partners. Delegate admins can manage customer tenants by passing their customer tenant ID during Connect-ExchangeOnline

 

$cred = Get-Credential
$customerTenant = “contoso-electronics.onmicrosoft.com”
Connect-ExchangeOnline -DelegatedOrganization $customerTenant -Credential $cred

 

Read more on how to use it in MFA PowerShell module here

Identity is now a positional parameter and it supports name/alias

The initial release of V2 module didn’t support using name and alias as Identity parameter. This was a conscious call to provide better performance of cmdlets as resolution of name and alias was a costly operation. However, with the constant feedback from preview community, we learnt that a lot of scenarios require quick data access for a small set (most commonly 1) of mailbox using PowerShell interactively. And in those scenarios having support for positional parameter and using name alias brings a lot of convenience.

For example:

 

Get-ExoMailbox -Identity contosoadmin@fabrikam.com

 

…can now be written as:

 

Get-ExoMailbox contosoadmin

 

Assuming contosoadmin is the alias of user contosoadmin@fabrikam.com of course.

Improved error handling, reduced data type differences and many more bug fixes

The latest version of client module contains bug fixes across Get-Help, unwanted session kills, almost all the properties have same data-type across RPS and V2 cmdlets thus reducing script migration overhead. Also, the dateTime property now honors the client-side locale and shows time according to your local machine time zone.

Please read the detailed release notes here

How do you get the best out of V2 cmdlets?

Use PropertySets and Properties parameters

Traditionally, RPS Cmdlets returned all mailbox properties in the output object. Most of these properties were not usually required but were part of the returned object which caused performance degradation.
In the new module we have bucketized certain related set of properties and called them “PropertySets”. These PropertySets are simply buckets of 2 of more Properties. We have exposed 2 new parameters in EXO Cmdlets: Properties and PropertySets.

  • PropertySets – it accepts one or more (in comma separated form) names of the properties buckets i.e. PropertySets. The following example will return all the properties mentioned in Minimum, Archive & Custom:

 

Get-ExoMailbox -PropertySets Archive, Custom

 

  • Properties – it accepts one or more (in comma separated form) name of the output property

 

Get-ExoMailbox -Properties LitigationHoldEnabled, AuditEnabled

 

You can specify PropertySets as well as Properties at the same time:

 

Get-ExoMailbox -Properties IsMailboxEnabled, SamAccountName -PropertySets Delivery
Get-ExoCASMailbox -Properties EwsEnabled, MAPIBlockOutlookNonCachedMode -PropertySets ActiveSync 

 

We have also introduced a new concept call “Minset” which is a bare minimum set of properties. If you don’t specify any PropertySets, you will get the bare minimum properties every time. If you specify a PropertySet while invoking a cmdlet, you will only get the “Properties” specified in the PropertySets parameter and you won’t get the properties listed in “Minimum” bucket.

Read more about property sets here.

Use Piping to get multi-threading benefit

Pipelines act like a series of connected segments of pipe. Items moving along the pipeline pass through each segment.  The V2 module invokes multiple threads on the client machine to parallelize execution and retrieval and thus provides a better performance in data retrieval.

V2 Cmdlets 1.pngIt can be clearly seen that for-looping took 900 seconds to get Mailbox Statistics for 100 mailboxes while it only took 48 seconds for the same operation using pipe operator. Nice!

What's Next?

Support for PowerShell Core

The V2 module works only on Windows PowerShell version 5.0 or lower. It doesn’t work on non-Windows Operating Systems i.e. Linux, Mac.

We plan to add the support for PowerShell 6 and 7 in the new V2 module so that it works seamlessly on Linux, Mac and windows.

Support for Automation using Certificate Based Authentication

Exchange Online management didn’t have official support for app-only scenarios i.e. background jobs authentication, scheduling etc. Currently, we are working on support app-only authentication using Certificates and Service Principal objects available in AzureAD. This is really important work and will help get you off Basic Authentication in Exchange Online, which as we hope you know, is being retired.

Frequently asked questions

How to handle the Windows 10 PowerShellGet Error?

For PowerShell version 5.1 which got shipped with Windows, a known issue causes an error during a module installation from PowerShell Gallery.The error message is shown below and the installation doesn’t succeed when this warning is shown:

Warning: The specified module ‘ExchangeOnlineManagement’ with PowerShellGetFormatVersion ‘2.0’ is not supported by the current version of PowerShellGet.

The current workaround is to forcefully install PowerShellGet using the below cmdlet:

 

Install-Module PowerShellGet -Scope AllUsers -Repository PSGallery -Force -AllowClobber

 

You will then need to re-load the PowerShell session; you can do this with the command:

 

PowerShell

 

You should then be able to successfully use the latest version of PowerShellGet

 

Install-Module -Name ExchangeOnlineManagement -Verbose -Scope AllUsers -Force

 

In case above steps doesn’t work for you, please read this on how to install the PowerShellGallery module manually.

Basic Auth still needs to be enabled on your client machine

The new PowerShell V2 module uses Modern Auth to establish connection for enabling all the 9 (as of this writing) REST-based V2 Cmdlets. In addition to V2 cmdlets, it also allows you to access 700+ of the older Remote PowerShell Cmdlets which requires a Remote PowerShell session to be established. Establishing an RPS session on Windows machine require WinRM BasicAuth to be enabled on the client machine even though it used Modern Auth mechanism to authenticate. The WinRM Basic Auth pipeline is essentially used for transporting Modern Auth tokens. If WinRM Basic Auth is disabled on the client machine, the new V2 cmdlets will continue to work (but the older RPS cmdlets will not)

We really hope you enjoy using the new Exchange Online V2 module, and we look forward to your feedback as we continue to improve them.

The Exchange Admin Team

25 Comments

PowerShell 7 is now out, so no excuse not to support it :) And yeah, automation! Keep up the good work, I like this monthly release cadence.

Microsoft

@Vasil Michev Support for PS 7/Core in an active work in progress and will be available for preview soon.

Occasional Contributor

@navgupta looking forward for the PowerShell 7 support :) ... i'm currently using with the -UseWindowsPowerShell switch to get around the limitation today, although it still doesnt import the older cmdlets Get-Mailbox etc.

 

a question around the v2 module though, when will we be able to use Get-EXORecipient -Filter against the company value ... today i have a lot of scripts which use Get-Recipient -Filter {Company -EQ 'XXX'} but this doesnt translate to Get-EXORecipient. is this because the underlying graph doesnt have a odata filter for the Company attribute?

New Contributor

Filter is absolutely critical to handling large tenants. Not only to allow selection of groups of users, but is used in conjunction with a “tracer” property update so you know which accounts have been processed when you have to restart the process due failures. 
Even with robust cloud command, account updates, such as adjusting audit settings, fail 2/3rds of the time when running processes that span days and sometimes weeks. (At least with about 165k of mailboxes)

Occasional Visitor

Is there documentation on how this new module connects out to the Internet?  I installed it on a Windows 2016 server where we have tools installed, but when trying to connect it fails with WinRM errors.  WinRM is running and does allow basic auth.  I suspect the proxy that outbound traffic is directed through is causing issues as this works from my Windows 10 laptop that doesn't use the datacenter proxy.

Microsoft

@JWare - The EXO V2 Module uses AzureAD user based authentication for the new Cmdlets. At the same time, it uses WinRM to establish remote session for running older RPS Cmdlets.

 

Please share your error in below format as described in documentation here - https://aka.ms/exops-docs

Microsoft

@UW_Scott - We are totally aligned with your thought here. Server side filters will be available in upcoming releases of the module.

 

However, you can always use filters on client side using 'Where-Object" as the new Cmdlets retrieve data significantly faster than their RPS counterparts.

 

 

Microsoft

@Jamie BRANDWOOD - You guessed it right. A lot of filterable properties are not available in odata thus making it harder to support filters on those.

 

Since, Get-EXORecipient is significantly faster than Get-Recipent, how about fetching the company value property for all recipients and using a client side filtering using "Where-Object" clause? 

Senior Member

Could you please confirm if the new EXO V2 module supports the national clouds, like Office 365 operated by 21Vianet in China?

Microsoft

@JWare : Proxies can be annoying.

This usually helps to resolve that:

 

$options New-PSSessionOption -ProxyAccessType IEConfig
Connect-ExchangeOnline -PSSessionOption $options

 

For the rest calls, it may be necessary to set up the default proxy settings for the .NET side of things before connecting:

 

[System.Net.WebRequest]::DefaultWebProxy = [System.Net.WebProxy]::new('<proxyurl>:<proxyport>')

[System.Net.WebRequest]::DefaultWebProxy.UseDefaultCredentials = $true

[System.Net.WebRequest]::DefaultWebProxy.BypassProxyOnLocal = $true

Contributor

Hello, I've reported this to the feedback email address as well, but the -Identity parameter fixes outlined in this post - seem to have only been applied to Get-EXOMailbox.

 

Get-EXO<everythingelse> still can only accept the Azure AD ObjectId/UserPrincipalName, or the EXO ExternalDirectoryObjectId/UserPrincipalName.

Get-EXOMailboxFolderPermission erroneously demands that a backslash comes after the colon in Identity.  However, when using the FolderId, rather than the FolderPath, the backslash shouldn't be there.

Contributor

Regarding the progress around Prefix, I think it would be nice to also have CommandName and FormatTypeName available as well.  If we only need to run 1 or 2 cmdlets, it's way faster/better to only download those 2 cmdlets (and optionally their format type data).  This idea is in the name of efficiency both for Microsoft and the customers.

Occasional Contributor

Any movement on Server Side filters or updates on levels of available filterable properties with an OData query ...?

Microsoft

@Jamie BRANDWOOD - Server side filters are a work in progress. A few wild card operators which ODATA doesn't support will not be available in the EXO cmdlets. Rest will be available. 

Occasional Contributor

I'm loving the new module so far, it's infinitely easier to script the install, maintenance, and connection, and I can't wait for cert based auth.

However, what is the plan for Exchange Online Protection? It was included in the V1 module, so are it's commands going to be made available in the V2 module as well, or is there another module in the works specifically for it?

Microsoft

Exchange Online Protection cmdlets are available in the latest version of EXO PowerShell V2 module published on 30th March.

Check https://aka.ms/exops-v2

Occasional Contributor

Great timing! I just updated and everything seems to be working well so far. Cheers!

Senior Member

This is awesome. We have few automations and been looking to  use CBA to authenticate. Is there any TAP program we can sign up for to help validate any scenarios.

Senior Member

I have a script in which I need to get the FolderPath for the Calender folder in each mailbox, for which I use Get-MailboxFolderStatistics. To test the performance I measured the time doing Get-MailboxFolderStatistics and Get-EXOMailboxFolderStatistics for all mailboxes. With the new and supposedly faster cmdlet this took 4x longer! Only when I ran the test a second time was it slightly faster (like 25%) than the old cmdlet, because it apparently uses caching.


If we cannot assume that the new cmdlets are at least not slower than the old ones, then I don't see the point in switching to them. So far I'm not impressed.

 

I also noticed that Get-Help -Online will open the wrong URL (it uses https://docs.microsoft.com/en-us/powershell/module/exchange/exchange-ps-v2-module/ when it should be https://docs.microsoft.com/en-us/powershell/module/exchange/powershell-v2-module/)

 

Microsoft

Hi @Gerard van der Land 

 

This is not expected. We would like to debug further and see why Get-EXOMailboxFolderStatistics is slower for you. We have not heard any feedback for it's slowness. Can you share the details at the email which gets printed when you do Connect-ExchangeOnline ?

 

We will take it up from there for further investigation.

 

Thanks

Exchange Online IT Admin Experiences Team

Senior Member

When can we expect certificate based auth support? Unfortunately we have lot of automation and we cannot leverage this module until CBA is supported.

Happy to help with any testing or validation.

Contributor

@Gerard van der Land I forget where it is documented but the first MS Graph based cmdlet execution is known to take a while as it sets up the MS Graph authentication.  The second and later commands are when you see the enhanced performance.

 

Where I've noticed the dramatic speed increase is with large large sets of data where it is now saving me many hours of script processing time.

Occasional Visitor

Hello Exchange team, 

 

The Microsoft code signing certificate you used for signing Exchange Online PowerShell v2 module has expired on May 2nd 2020. 

 

Kind regards, 

 

Dejan Foro 

dejan.foro@exchangemaster.ch 

Exchangemaster GmbH 

www.exchangemaster.ch

Regular Contributor

Is it me only, who need "get-mailuser" and all related cmdlet, but is unable to find them from new module (0.4578.0)? 

 

Edit: :flushed:

Working again.

Occasional Contributor

Any news on the PS7 support front?