New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EXOInboundConnector not in desired state output false but the settings where correctly applied/configured in a tenant #2180
Comments
Could you share the verbose log of the Test-DSCConfiguration or the Event Log items? Within the Windows Event Log there should be a full overview of which settings are marked as drifted. |
Here it is: Log Name: M365DSC Log Name: M365DSC |
This one marks the value of |
Sorry, I was out of office. I will have a look on this during the next days. |
EXO stores the value of sender domains as smtp:;1 e.g. contoso.com is smtp:contoso.com;1 or * is smtp:*;1 |
Details of the scenario you tried and the problem that is occurring
EXOInboundConnector below settings are correctly applied/configured in our tenant but I don't understand why are they 'NotInDesiredState'.
When I run the following commands in the Power-Shell everything seems to be working fine for EXOInboundConnector:
but the following Power-Shell command
outputs the EXOInboundConnector not in desired state
The DSC configuration that is used to reproduce the issue (as detailed as possible)
MOF file extract:
The text was updated successfully, but these errors were encountered: