Performance Issues with Outlook When Delegating Large Mailboxes (Exchange Online)
Hello! We're using Exchange Online, and most users access their mail through the Outlook (classic) desktop app. A common scenario in our organization is that users need temporary access to a coworker’s mailbox when that person is out on PTO. We typically grant this via mailbox delegation (Read and Manage + Send As), and the mailbox remains a standard UserMailbox, not converted to a shared mailbox. The issue: When the delegate accesses the mailbox, Outlook often becomes sluggish or unresponsive, presumably due to syncing the delegated mailbox — these are usually large (30–40 GB). We've noticed major performance degradation during this sync process. What I’ve Tried: Unchecked "Download Shared Folders" (Account Settings > Account Settings> Change > More Settings > Advanced) Adjusted Offline Cached Exchange Mode to sync fewer months Unfortunately, these haven't resolved the issue. My Questions: Is there a way to delegate access without triggering a full sync of the mailbox data to Outlook? (Users are not open to switching to OWA as they rely heavily on Outlook for their primary mailbox.) What’s the best practice for temporarily granting access to large mailboxes in Exchange Online without impacting Outlook performance? Any insights or workarounds would be greatly appreciated! Thanks in advance! -AdamLocal printers & universal printer connector & server delegation
Hi everyone, we have 2 people managing "Universal Print" in our company. We installed the connector on one server and you have to add the printers, remove old etc. Is there any way to do JIT rights with no 3rd party tools? As this is a task that happens one time every 3 months i do not want to give them admin rights to a server. Following the least privilege principle Windows Admin Center maybe? What is your solution on this? Best regards Stephan
Call Delegation with Direct Routing
Hi, I need a little help with the Call Delegation feature, specifically calling on behalf of somebody. I've set User 1 as a delegate for User 2, however when he calls a PSTN number on his behalf (from the desktop client), the call shows User 1's DID as the Caller ID, not User 2's as expected. I've checked the trace on our Direct Routing SBC, and I see User 1's SIP URI in From: header field of the INVITE coming from Teams side - no matter if User 1 selects to call on behalf of User 2 or not. Also no other headers that could help the SBC distinguish between these calls. Am I missing something here?
