admin
717 TopicsExchange Mailbox doesn't work on native Apple Mail-Clients (iOS and macOS)
Hey there, Since mid of 2026 my tenants users aren't able to connect the Exchange Mailbox over the native Apple Mail-clients. Earlier this year the macOS Mail Client which worked with the old EWS (Exchange Web Service) hast stopped working and some month later (since September) the iOS Mail-Client with Active Sync. EWS is still enabled in our organization and Windows Computers are able to pull their Mailbox over the legacy Outlook-Clinet (which also run on EWS). Is this a known issue? Will it get fixed on Apple or Microsoft side? Or are we forced to use Outlook App in future? Best Lenny48Views0likes2CommentsExchange SE Extended Protection
Hello Exchange On Prem admins. As we laugh in the face of service level outages I would like to share some tips and tricks to running Exchange SE in extended protection mode. The most critical component of enabling extended protection on IIS is the DNS namespace and the corresponding SAN that is attached to the certificate therein. Exchange is not entirely namespace aware, so what your clients connect to is not what it uses for internal operations such as eDiscovery through ECP and the Proxy healthset. Here are some tweaks that have made my environment run without errors : When using eDiscovery through the ECP your IIS cert must have the server FQDN in the SAN. When observing the proxy test monitor health sets, they use HTTPS://LocalHost, so localhost must be in the SAN. When configuring IP lock down the Exchange CSS script does not capture all of the applicable IPs that backend IIS operations operate on : Calls are made from the replication network, the user facing interfaces and the hidden 169.254.X.X DAG network. If you are multihomed and using IP restriction in IIS, make sure you include all of these networks, as it seems to choose at random. Stay secure, and stay on prem.37Views0likes0CommentsExchange Online Plan 1 and Planner
Now that Microsoft have confirmed they will kill Wunderlist/To-Do, what is planned for customers with an Exchange Online Plan 1 which use To-Do alongside Exchange/Outlook? As usual, Microsoft's official support announcment https://support.microsoft.com/en-us/planner/to-do-to-planner creates more questions that customer are faceing now than providing answers.64Views0likes2CommentsIp exchange on spamlist
Have noticed that a range of Microsoft IP's are on blacklists. Examples (there is a whole range of them): 52.101.66.97 Listed on spamcop. 52.101.66.97 Listed on: 0SPAM Sender Score Reputation Network SORBS SPAM Emails from Exchange Online systems or those using Outlook Protection are being delayed to us by several hours. https://0spam.org/request?ip=52.101.66.97177Views0likes1CommentWhy do Apple macOS and Ubuntu clients display Exchange meeting times one hour earlier than scheduled
If a meeting is generated from Apple macOS and Ubuntu clients showing the meeting time as one hour earlier than the actual scheduled time email solution is exchange server 2019, what will be the issue.349Views0likes1Comment550 5.7.705 Tenant Email Block 55+ Hours - Support Unresolved
Our M365 tenant (labaradorpake.onmicrosoft.com) has been blocked from sending outbound email for over 55 hours with error 550 5.7.705 Access denied, tenant has exceeded threshold. Despite multiple support tickets and promises of 24-hour resolution, the block remains active. **Error Details:** - NDR: 550 5.7.705 Access denied, tenant has exceeded threshold - Scope: External outbound email only is blocked; internal tenant-to-tenant email works fine - Microsoft Defender Restricted Entities page shows 0 restricted users — the block is at tenant level, NOT user level - No transport rules exist that could be blocking outbound - No alerts in Exchange Admin Center **Timeline:** - June 19: Support ticket #2606190040005588 created, agent Manisha confirmed remediation complete and promised block would be lifted within 24 hours - June 21 (55+ hours later): Block STILL ACTIVE. Manisha has not responded to follow-ups. - June 21: Created 2nd ticket #2606210040000778, assigned to agent Odunayo — no action taken - June 21: Created 3rd ticket #2606210040000844 with phone callback request — no callback received yet **What we have tried:** 1. Three Microsoft support tickets (all Sev C) 2. Escalation emails to agent, tech lead, team manager (all bounce due to tenant block preventing outbound email) 3. Support Assistant chat bot — cannot escalate to human agents 4. Azure Portal support — No Access for this tenant tier 5. getsupport.microsoft.com — No Access 6. Microsoft Learn Q&A post: https://learn.microsoft.com/en-us/answers/questions/5926147 7. Phone callback requested on 3rd ticket — still waiting **Critical Impact:** The tenant cannot send ANY external email. All outbound messages to external recipients bounce with 550 5.7.705. This is a complete business email outage that has persisted for over 55 hours despite Microsoft support confirming remediation was complete. Has anyone experienced a similar tenant-level block (550 5.7.705) that took this long to resolve? What escalation paths actually work when support agents are unresponsive? Any advice on getting this block lifted urgently would be greatly appreciated. Cross-posted from Microsoft Learn Q&A: https://learn.microsoft.com/en-us/answers/questions/5926147399Views0likes3CommentsExchange 2010 to Microsoft 365 Migration – Recommended Approach and Tools
I’m looking for guidance on migrating Exchange 2010 (on-premises) to Microsoft 365 / Office 365. Is a direct migration from Exchange 2010 supported, or is an intermediate hop (such as upgrading Exchange or setting up a hybrid configuration) required? Additionally, could you please recommend any reliable tools that can help with this migration? I also have a few PST files that need to be migrated as part of the process. I’d appreciate insights on best practices, common challenges, and lessons learned from real-world migrations. Thanks in advance for your help.1.3KViews0likes5CommentsDepreciation of Custom Controls in favor of External MFA
Deprecation of Custom controls Custom controls are being deprecated in favor of External MFA. Existing configurations keep working during the transition, but you should begin migration planning now. Custom controls retire September 30, 2026, and reach end of life in May 2027. When will you see this change? Custom controls will be retired on September 30, 2026, and the service will reach end of life in May 2027. Who will be affected by this change? This update affects organizations currently using Custom controls to integrate third-party MFA providers with Conditional Access. How will this affect your organization? Organizations relying on Custom controls will need to transition to External MFA to maintain support and continue using third-party MFA solutions within Microsoft Entra ID. Moving to External MFA also enables more consistent Conditional Access enforcement and improved integration with Microsoft Entra security capabilities. What do you need to do to prepare? Organizations should: Review existing Custom controls integrations Evaluate External MFA migration requirements Test Conditional Access policies and user experiences before migration Begin migration planning ahead of the retirement date Read more in the External MFA General Availability announcement and migration guidance.591Views0likes0CommentsRemove-Calendarevents
VasilMichev and TonyRedmond Does it need permission on Termed employees calendar? i am Global Admin and when i run this command with preview it does not preview any results Remove-CalendarEvents -Identity james.bond@domain.com -CancelOrganizedMeetings -QueryStartDate 11-7-2016 -QueryWindowInDays 120 -PreviewOnly -Verbose5.4KViews0likes9Comments