The term 'Get-o365DynamicDistributionGroup' is not recognized as the name of a cmdlet

[smtp25gmailcom]

It can't find this command 'Get-o365DynamicDistributionGroup' and it also fails for get-o365outboundconnector

[12/21/2022 12:29:23 AM] - Starting collection of dynamic distribution groups. invoke-command : The term 'Get-o365DynamicDistributionGroup' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At C:\Program Files\WindowsPowerShell\Modules\DLConversionV2\2.9.4\Get-O365GroupDependency.ps1:144 char:34

• ... $functionTest += invoke-command -scriptBlock $scriptBlock

• 
  + CategoryInfo          : ObjectNotFound: (Get-o365DynamicDistributionGroup:String) [Invoke-Command], CommandNotFo 

[smtp25gmailcom]

test-outboundConnector : The term 'get-o365OutboundConnector' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At C:\Program Files\WindowsPowerShell\Modules\DLConversionV2\2.9.4\DLConversionV2.psm1:2187 char:9

• test-outboundConnector -overrideCentralizedMailTransportEnabl ...

• 
  + CategoryInfo          : ObjectNotFound: (get-o365OutboundConnector:String) [Test-OutboundConnector], CommandNotF 
  oundException
  + FullyQualifiedErrorId : CommandNotFoundException,Test-OutboundConnector

[smtp25gmailcom]

ok - I can see why I get this error. For those finding this O365 is the prefix added to commands so they are differentiated from the onpremise cmds, this prefix is specified when the module connects to EXO. When I manually connect to EXO those commands don't exist (get-outboundconnector)for me either. I must be having brain fade because I can't see why. I have exchange admin role active and global just for good measure

[timmcmic]

If you’re having to run connect-ExchangeOnline first something else is wrong. Make sure the account your using is not implementing mfa or use certificate auth. The script should be able to establish the connection non-interactively,

Generally when I see this someone has to have an interactive logon first - so they leverage the ability that the new commands do not clobber existing commands on import.

Tim

============================== Timothy J. McMichael Senior Support Escalation Engineer @.**@.> (980)-776-7465

Hours: Sunday – Wednesday 08:00 – 16:00 eastern time zone.

Manager: Tom Roughley @.**@.>)

Premier Support - (800)-936-3100 Broad Commercial Support - (800)-936-4900

==============================

---

From: smtp25gmailcom @.> Sent: Tuesday, December 20, 2022 7:58 PM To: timmcmic/DLConversionV2 @.> Cc: Subscribed @.***> Subject: Re: [timmcmic/DLConversionV2] The term 'Get-o365DynamicDistributionGroup' is not recognized as the name of a cmdlet (Issue #100)

ok - I can see why I get this error. For those finding this O365 is the prefix added to commands so they are differentiated from the onpremise cmds, this prefix is specified when the module connects to EXO. When I manually connect to EXO those commands don't exist for me either. I must be having brain fade because I can't see why. I have exchange admin role active and global just for good measure

— Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ftimmcmic%2FDLConversionV2%2Fissues%2F100%23issuecomment-1360618230&data=05%7C01%7Ctimmcmic%40microsoft.com%7C72870976c53645666a3b08dae2ee757e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638071811050390853%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vlVf%2FIhL7ZY939VSreL7ebjgnopedjNJiLeYLOuxNT4%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKGTN6I2RQVGDIVFKDQSPRDWOJI25ANCNFSM6AAAAAATFCB45U&data=05%7C01%7Ctimmcmic%40microsoft.com%7C72870976c53645666a3b08dae2ee757e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638071811050390853%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=SOAp2bh34esfFd7XVTvT1G%2BHbr%2BncnBmTX1A8xvoURY%3D&reserved=0. You are receiving this because you are subscribed to this thread.Message ID: @.***>