This is something, which cannot be stressed enough:
When you flag e-mails or calendar items as private, it will not ensure privacy!
You might argue that you have not granted “Delegate can see my private items”, but this is ONLY honored by certain clients and in certain conditions.
Continue readingMicrosoft Graph is gaining more and more attention by developers. Also due to the fact of deprecation of Basic Authentication (please read more about this here!), many are shifting to the new protocol.
I welcome this change, but what I just came across is something I don’t like:
A colleague opened a ticket and complained about something is modifying his calendar items. So far, I saw this an easy task and used my Get-CalendarItems script, but I had to learn not everything is logged, when Microsoft Graph is used…
I got word that the multi-geo issue will be addressed. No ETA as of now. But at least for calendar items a fix is currently rolling out. Now the used AppID is logged:
The only drawback: Looks like every component team is doing their own thing. That’s why we don’t see proper entries on the item in the Sent Items folder.
Continue readingLast week fellow MVP Vasil Michev (his very valuable blog can be found here!) stumbled across a post on Spiceworks, related to compliance feature in Exchange.
After some testing, i was able to reproduce the issue as well. As this is really a severe bug, a SevA case was opened at my companies account.
You can read and get the full details on Tony’s post here.
Note: I’ve tested this in my companies environment with the same Outlook client against Exchange 2016 CU14 and couldn’t reproduce the issue.
Once we have the root cause for this issue, you will be informed. Until then I can only recommend to open a ticket with MS.
The clueless guy 