Adam

Well the good news is that the format used by the SMLets Exchange Connector is the same format as the Microsoft Exchange Connector. In which case, the logic you have...

Previous commit was pushing #411 from primary to dev branch

Looks like this occurs given the following: - Using Exchange Online - **_Not_** using Run As Accounts/getting the password into the script by some other means In any case, much...

I was a bit too quick to close this. I merged this into dev and will keep this issue open for the sake of transparency.

Please re-open/create a new pull request if you'd like to pursue this further.

I feel like you are onto something here by forcing the ID to be unique with a GUID. But the thing is, I can't reproduce the scenario you're referring to...

> But in the actual script only the username was used, which causes the issue Are you referring to the following line in New-CMDBUser? or somewhere else? https://github.com/AdhocAdam/smletsexchangeconnector/blob/02be0b1aed028647848c982e19ae5779c7596822/smletsExchangeConnector.ps1#L2916C9-L2916C209 > I...

I've been doing some extensive testing of this proposed change @alexaxb. I had a question/scenario that I'm not sure needs to be handled, but seems worth bringing up if we're...

Can you reproduce on demand @pwahlmueller? If so, it'd be great to get some PowerShell debugging events by running the connector manually (ISE or VS Code) and see what (if...

If the... - logging level is 4/verbose - the item is in the inbox - it's unread even after a run of the connector - the connector isn't recognizing it...