search

microsoft / Microsoft365DSC

Manages, configures, extracts and monitors Microsoft 365 tenant configurations
https://aka.ms/M365DSC
MIT License
1.6k stars 500 forks source link

Issue to connect to security and compliance center #2140

Closed flaviusmp closed 2 years ago

flaviusmp commented 2 years ago

Hello,

When I am using the export command it is failing the connection to the security and compliance center. It returns the following error:

"Connecting to {SecurityComplianceCenter}...❌ Processing data from remote server eur02b.ps.compliance.protection.outlook.com failed with the following error message: The request for the Windows Remote Shell with ShellId A93A8F63-27FC-4 041-97D2-81625BD2CB0E failed because the shell was not found on the server. Possible causes are: the specified ShellId is incorrect or the shell no longer exists on the server. Provide the correct ShellId or create a new shell and retry the operation. For more information, see the about_Remote_Troubleshooting Help topic. Partial Export file was saved at:........ "

Can you please assist? I have the latest version installed:

PS C:\windows\system32> Get-InstalledModule microsoft365dsc

Version Name Repository Description

1.22.720.1 Microsoft365DSC PSGallery This DSC module is used to configure and monitor Microsoft tenants, including SharePoint Online, Exchange, ...

Best regards.

NikCharlebois commented 2 years ago

Is this happening on every run? I've seen cases were the connection expired on the server side. Try closing all PowerShell console and try to replicate. Thanks

flaviusmp commented 2 years ago

Hi, yes it happens all the time. I tried also to reboot the server and still get the same error. Regards.

NikCharlebois commented 2 years ago

What command are you calling when you get the error? E.g., Export-M365DSCConfiguration with credentials?

aflopex commented 2 years ago

Good Morning @NikCharlebois , I am having a similar issue connecting to the SCC with this month's export of the SCC configuration. In my case, I don't get an error but instead, when I execute Export-M365DSCConfiguration, the commands are trying to authenticate differently by invoking an Azure sign-in which is of course blocked by our server's browser settings as you can see in the image below. I am not sure if something change in the way that M365 DSC now authenticates to SCC or if my permissions to SCC have changed. As of right now, I am only using Credentials for the MS Teams and SCC exports and App/Cert based for all others. Can you confirm if the authentication method for SCC exports changed? Any help you get give will be greatly appreciated. Andres

image

andikrueger commented 2 years ago

SCC is still using Credential based authentication. There was no change to that. https://microsoft365dsc.com/user-guide/get-started/authentication-and-permissions/#authentication-methods

Anyways: Could you please update to the latest version of M365DSC as there were some authentication improvements and please check with your IT Dep. to change the cookie policy for Microsoft 365.

Update-Module Microsoft365DSC
Update-M365DSCDependencies
Uninstall-M365DSCOutdatedDependencies
andikrueger commented 2 years ago

Closing due to inactivity.

aflopex commented 1 year ago

Good Afternoon @Nik @.***> and M365DSC Team,

I did follow your instructions below to update to the latest ver of the module (.1102) and I am still not able to connect to the SCC on any of my 20 tenants and obtain a DSC export. Please see the event I get as well as the code I am executing. I also confirmed that my credentials are a GA on the tenant and I was able to get the MS Teams DSC export using the same creds.

image

@.*** image

@.***

From: Andi Krüger @.> Sent: Friday, September 23, 2022 5:09 AM To: microsoft/Microsoft365DSC @.> Cc: Lopez, Andres @.>; Comment @.> Subject: [EXT] Re: [microsoft/Microsoft365DSC] Issue to connect to security and compliance center (Issue #2140)

CAUTION: This email originated from outside MetLife. Do not click links, open attachments or forward unless you recognize the sender and their email address and if you were expecting an email from them. If you suspect this email is phishing, report it by clicking on the Report Phishing button or forward it to @.**@.>.

SCC is still using Credential based authentication. There was no change to that. https://microsoft365dsc.com/user-guide/get-started/authentication-and-permissions/#authentication-methods

Anyways: Could you please update to the latest version of M365DSC as there were some authentication improvements and please check with your IT Dep. to change the cookie policy for Microsoft 365.

Update-Module Microsoft365DSC

Update-M365DSCDependencies

Uninstall-M365DSCOutdatedDependencies

— Reply to this email directly, view it on GitHubhttps://github.com/microsoft/Microsoft365DSC/issues/2140#issuecomment-1255969473, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMERPBBJKVU3GJ2XUTJLAHTV7VXRRANCNFSM54VJTMWQ. You are receiving this because you commented.Message ID: @.**@.>>

The information contained in this message may be CONFIDENTIAL and is for the intended addressee only. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the sender immediately and delete this message.