Forum Widgets
Latest Discussions
Welcome to the Microsoft Exchange: Post Ignite AMA!
Welcome to the Microsoft Exchange: Post Ignite Ask Microsoft Anything (AMA)! This live hour gives you the opportunity to ask questions and provide feedback directly to the team regarding some of the recent news and updates from Microsoft Ignite. Please introduce yourself by replying to this thread. Post your questions in a new thread within the Exchange AMA space, by clicking on, "Start a New Conversation" at the top of the page.
Tenant to Tenant Migration
At Ignite the Session "Supporting Mergers, Acquisitions, and Divestitures in Microsoft 365" gave a nice overview about the future T2T-Migration-Capabilities. I am located in Switzerland and I have tried to walk through the T2T-Mailbox-Migration https://docs.microsoft.com/en-us/microsoft-365/enterprise/cross-tenant-mailbox-migration?view=o365-worldwide Question: does this preview also work in the EU-Datacenters (including the Datacenter in Switzerland)? The preparation Script definitely seem to be written for US-Locations (especially for the Azure KeyVault-Setup).
Exchange Monitoring
Hi guys, at Ignite 2018 some roadmap items have been communicated for Exchange on Prem, one of them was enhanced Monitoring capabilities - as the current SCOM integration of the HM components is far from being optimal. Any news in that space, is this still on the roadmap & can you share any details? Thanks! MartinAnnouncing a Microsoft Exchange AMA!
We are very excited to announce a Microsoft Exchange Post Microsoft Ignite 'Ask Microsoft Anything' (AMA) for Microsoft Exchange! The AMA will take place on Thursday, October 8th, 2020 from 9:00 a.m. to 10:00 a.m. PT in the Microsoft Exchange AMA Space Add the event to your calendar and view in your time zone https://www.myeventurl.com/Events/Details/159. An AMA is a live online event similar to a “YamJam” on Yammer or an “Ask Me Anything” on Reddit. This AMA gives you the opportunity to connect with members of the product engineering team who will be on hand to answer your questions and listen to feedbackExchange Mail flow - Manager Approval for PII
We have configured Exchange mail flow rules to route outbound emails containing Confidential information (PII such as ssn, credit card, etc), to the sender's manager for approval/rejection. This is working as expected. However we cannot seem to find a technical solution to have emails matching these rules automatically be sent to another manager/person / group, in the event the sender's manager is Out of Office. The goal is to automated the emails re-routing without having to manually create new rules every time a manager is out of office and cannot approve emails. Any ideas?
Exchange Hybris and Azure Cloud Provisioning
Maybe a too in depth question for this forum but I have a scenario leveraging Azure AD Cloud provisioning and remove the hybrid exchange configuration allowing a customer to manage the exchange attributes of users directly in EXO rather than having one Exchange server on premises to enable editing of user exchange attributes. My customer wants to decomm all on premises exchange servers. Is this even an option or am I barking up the wrong tree 🙂
Is the default ban on external forwarding for ATP customers only?
Hi, I've seen contradictory documentation about the new setting that will automatically block external forwarding of mail from a user mailbox (see https://www.vansurksum.com/2020/08/25/microsoft-is-making-changes-related-to-automatic-email-forwarding-for-atp-customers-here-is-what-you-need-to-know/). Is this just for customers with ATP or will it impact deployments that are using only EOP?60 users
https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/set-up-anti-phishing-pol... We are a large government agency and have more than 60 users to protect from being impersonated as message senders. Is the # of 60 users a tenant wide limitation? We have created multiple policies and each policy have 60 users but it did NOT work. Only 60 users on the first policy get protected. The next 60 users on the next policy did not get protected.Impersonation settings in ATP anti-phishing policies
We are a large government agency and have more than 60 users to protect from being impersonated as message senders. https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/set-up-anti-phishing-policies?view=o365-worldwide#impersonation-settings-in-atp-anti-phishing-policies Is the # of 60 users a tenant wide limitation? We have created multiple policies and each policy have 60 users but it did NOT work. Only 60 users on the first policy get protected. The next 60 users on the next policy did not get protected.
