PowerShell 5: M365SATTester.ps1 not authenticating the Exchange/Security Compliance properly

[secopsadminz]

[Karmakstylez]

Hello,

Please confirm the following:

• What version are you using of Microsoft Exchange PowerShell?
• Which Windows Version are you using?
• Which PowerShell are you using?

Thanks in advance.

~LvdW

[secopsadminz]

Hello,

Please confirm the following:

• What version are you using of Microsoft Exchange PowerShell?
• Which Windows Version are you using?
• Which PowerShell are you using?

Thanks in advance.

~LvdW

Powershell version 5.1.26100
Windows 11
I cannot find any exchange PowerShell version. There is no exchange on premise. I searched and everything I find for exchange points to exchange management console. So if this part is for exchange on premise could that be the issue I have? How can I get around this? Thanks

[Karmakstylez]

Hello @secopsadminz ,

Please run:
Get-InstalledModule -Name "ExchangeOnlineManagement"

You will get the result. If you do not get the result use Get-InstalledModule and search for Exchange.

Please report back at me which version you have else I cannot reproduce the issue.

~LvdW

https://learn.microsoft.com/en-us/powershell/module/powershellget/get-installedmodule?view=powershellget-3.x

[secopsadminz]

Hello @secopsadminz ,

Please run: Get-InstalledModule -Name "ExchangeOnlineManagement"

You will get the result. If you do not get the result use Get-InstalledModule and search for Exchange.

Please report back at me which version you have else I cannot reproduce the issue.

~LvdW

https://learn.microsoft.com/en-us/powershell/module/powershellget/get-installedmodule?view=powershellget-3.x

Exchange online powershell version 3.7.2

[Karmakstylez]

Thank you. That seems to be the latest version. Did you try to remove 3.7.2 and check if 3.6.0 is working properly? For now 3.7.2 and the latest version only works on Linux and Non-WAM devices which fallback to browser authentication:

Install-Module -Name ExchangeOnlineManagement -RequiredVersion 3.6.0

Have you run the Installation PowerShell 5.1 (Windows) instructions as well? I know there are some issues with the PowerShell 5 mechanism as I am looking into it. It might occur that there are breaking changes in cmdlets and we need to migrate to PowerShell 7 in order to keep compliancy and other things correctly working.

~LvdW

P.S. I strongly advice you to use PowerShell 7 for the best results. I am currently looking into the issue with the WAM disablement as that is forwarded to the ExchangeOnlineTeam but I haven't heard back from them yet.

[secopsadminz]

Thank you. That seems to be the latest version. Did you try to remove 3.7.2 and check if 3.6.0 is working properly? For now 3.7.2 and the latest version only works on Linux and Non-WAM devices which fallback to browser authentication:

Install-Module -Name ExchangeOnlineManagement -RequiredVersion 3.6.0

Have you run the Installation PowerShell 5.1 (Windows) instructions as well? I know there are some issues with the PowerShell 5 mechanism as I am looking into it. It might occur that there are breaking changes in cmdlets and we need to migrate to PowerShell 7 in order to keep compliancy and other things correctly working.

~LvdW

P.S. I strongly advice you to use PowerShell 7 for the best results. I am currently looking into the issue with the WAM disablement as that is forwarded to the ExchangeOnlineTeam but I haven't heard back from them yet.

I will try to install the 3.6.0 and repost back. The nI will try to install PowerShell 7. thanks

[secopsadminz]

Thank you. That seems to be the latest version. Did you try to remove 3.7.2 and check if 3.6.0 is working properly? For now 3.7.2 and the latest version only works on Linux and Non-WAM devices which fallback to browser authentication:
Install-Module -Name ExchangeOnlineManagement -RequiredVersion 3.6.0
Have you run the Installation PowerShell 5.1 (Windows) instructions as well? I know there are some issues with the PowerShell 5 mechanism as I am looking into it. It might occur that there are breaking changes in cmdlets and we need to migrate to PowerShell 7 in order to keep compliancy and other things correctly working.
~LvdW
P.S. I strongly advice you to use PowerShell 7 for the best results. I am currently looking into the issue with the WAM disablement as that is forwarded to the ExchangeOnlineTeam but I haven't heard back from them yet.

I will try to install the 3.6.0 and repost back. The nI will try to install PowerShell 7. thanks
Hi, sorry for the the delay. I tried th e3.6.0 no luck. I installed push 7 al modules. Ran the Connection tester and fails to connect to Sharepoint. Specified method is not supported. There is a message above it about Sept 9th 2024 and connect with interactive. It says to refer to some pnp.github docs for how to register an application. Any ideas on this ? Thanks

[secopsadminz]

Thank you. That seems to be the latest version. Did you try to remove 3.7.2 and check if 3.6.0 is working properly? For now 3.7.2 and the latest version only works on Linux and Non-WAM devices which fallback to browser authentication:
Install-Module -Name ExchangeOnlineManagement -RequiredVersion 3.6.0
Have you run the Installation PowerShell 5.1 (Windows) instructions as well? I know there are some issues with the PowerShell 5 mechanism as I am looking into it. It might occur that there are breaking changes in cmdlets and we need to migrate to PowerShell 7 in order to keep compliancy and other things correctly working.
~LvdW
P.S. I strongly advice you to use PowerShell 7 for the best results. I am currently looking into the issue with the WAM disablement as that is forwarded to the ExchangeOnlineTeam but I haven't heard back from them yet.

I will try to install the 3.6.0 and repost back. The nI will try to install PowerShell 7. thanks
Hi, sorry for the the delay. I tried th e3.6.0 no luck. I installed push 7 al modules. Ran the Connection tester and fails to connect to Sharepoint. Specified method is not supported. There is a message above it about Sept 9th 2024 and connect with interactive. It says to refer to some pnp.github docs for how to register an application. Any ideas on this ? Thanks

Ran the M365SATTester. It looks like it gets going then throws this error. I do get successful popups with logons. Bot sure where this is coming from >>>

[secopsadminz]

Do you think I should try this on linux instead of windows 11?

[Karmakstylez]

Hi @secopsadminz ,

Thank you for providing me the information.

I cannot guarantee that in your situation Linux will work as it seems to be either a problem with the modules here or the environment.

According to the script it fails to retrieve an organization name.

Can you please do the following:

1. Remove all the installed PowerShell modules manually via Program Files
2. Reinstall the modules using PowerShell 7 as the procedure in Alpha using Install-Module or Install-PSResource if you have the newer version of PSGet.
3. Edit your M365SATTester.ps1 and configure it to the following:

$ScriptConfig = @{
    OutPath          = "C:/Out"
    Username         = "example@example.org"                        # Replace with your username
    EnvironmentType  = 'M365'
    Modules          = "All"
    LicenseMode      = "E3"
    LicenseLevel     = "All"
      ReportType       = "HTML"
    AllowLogging     = [switch]::Present
    LocalMode        = [switch]::Present
    SkipChecks       = [switch]::Present
}

4. Run the M365SATTester.ps1 with PowerShell 7
5. Check if you are getting any error at any point.

Repeat the steps 1 till 3 but instead follow the PowerShell 5 instructions.

Further questions so I can verify if things are working:

• Do you have an Azure Environment and / a registered .onmicrosoft tenant name which you are trying to audit as it seems it couldn't get the environment name.
• Please run this command to see if you have an organization name: $OrgName = (((Get-MgOrganization).VerifiedDomains | Where-Object { $_.Name -like "*.onmicrosoft.com" -and $_.Name -notlike "*mail.onmicrosoft.com" }).Name -split '.onmicrosoft.com')[0]
• Check with $OrgName if it gives the OrgName back. If this does not give anything back please use the following command: ((Get-MgOrganization).VerifiedDomains).Name to see if you are getting Verified Domainnames back.
• You can also use the ExchangeOnlineManagement cmdlet: Get-AcceptedDomain to check which domains are there.

Kindly let me know the information so I can see where to look and further test.

~LvdW

[secopsadminz]

I tried on a new windows 11. Followed steps for PowerShell 7. Ran the M365SATTestee.ps1. The security / compliance connected but now I get a failure on SPOService or Sharepoint connection. The error Connect-SPOService . I think Sharepoing connected on the other system I was using. Maybe something sis not get installed? screenshot >>>