Disabling Calendar Repair Assistant on mailboxes in Exchange Onprem 2019
Hi, We are in Exchange Hybrid setup were some mailboxes are in cloud and onprem. Recently, there were some issues with Calendar events were recipients weren't notified of any updates for the events, sometimes the updated event would have been cancelled by recipient and the recipient didn't even know that they received update and it was automatically cancelled by them.... This was a normal situation for EAs for their executive calendar events When raised a ticket with Microsoft on this issue, Microsoft collected CDL logs and found that CRA was kicking in each time when there was an update and was reverting the updated meeting request to the previous cancellation and as we know this is not a bug, this is just how the CRA works...So, Microsoft is like CRA is a legacy feature with limited applicability and functionality in the current exchange environment and hence has asked to disable-CRA in On-prem exchange as this will not affect normal calendar usage for users. I had disabled for 5 users and they have reverted that they are not seeing any issues post disabling CRA. so before gunning down on all mailboxes I wanted to take a second opinion on whether is it safe to disable CRA for alll mailboxes in Exchange OnpremIs the Archive mailbox self-help diagnostic working for anyone?
Just curious: is the archive mailbox self-help diagnostic at https://aka.ms/PillarArchiveMailbox working for anyone? When I run it, instead of getting results about the user whose UPN I entered, I get this: The following issues were found with your archive mailbox. No account was found for [The UPN of my admin account]. Make sure you've entered the correct email address or create a new account with that name. For more information, see Add users to Office 365. I tried opening a ticket with Microsoft Support, but they refused to work on it without requiring me to do all the legwork of gathering logs and HAR traces and who knows what else, despite the fact that the support agent was able to replicate the exact same issue in his lab.
Issue with certificate renewal for exchange Edge Transport Server
Hello team, I have come across a very particular problem I deployed 2 exchange server 2019 with one edge transport server When we are renewing the Certificates with wildcard certificate on both mailbox server ,and on edge transport server ,it is impossible for me to renew the edge subscription It says the cerificate is in "doublon" (repetitive) on one of the Exchange servers.I have always been using same certificate on exchange server be it edge or mailbox I tested a bogus different certificate on mailbox and on edge,only then th e edge sync works Did anybody come across this issue. Thanks
Email Showing as Quarantined in a Message Trace, but Not Showing up in MS Defender
A customer of ours was waiting on an email to arrive and to help figure out where the email was or if it was sent yet we ran a message trace. The message trace showed that the email was sent to quarantine. With this information in mind, I went to MS Defender > Email & collaboration > Review > Quarantine but could not find the message. I modified some of the filters and could not get the quarantined message to appear. I triple checked the filters I created and made sure the information was correct. I also removed all filters and looked for the time period the email came in, but could not find it. Not sure if this is related, but this email had a significant delay likely coming from the sender. Any thoughts or ideas? Or anything that I am missing?
Mailbox for Service Account (exchange online)
Hi Our organisation isn't ready to move to Exchange Online yet, though we have Office 365 e3 licencing. I need to create a service account that can send emails via Outlook 365 for use In Power Automate. The documentation I have seen for adding a mailbox to an existing AAD user requires assigning an exchange licence to the account via the licence portal. I can't see any such licences though we do have e3 licencing which are visible that I assume covers this? Unfortunately the admin who did the original configuration has moved on and I don't have a global admin role so have to go through a support team that can't help me with my lack of knowledge in the area! Any advice would be very much appreciated as what ( i think) should be a simple task has taken a lot of time to try and get to the bottom of! Thanks, Dale.
Can we hide default address lists in Outlook Address Book and show only custom ones?
There are existing Custom Address Lists. When users use the MS Outlook App (Office 2019) and open the Address Book, is it possible to hide the other address lists (including domain-sg-GAL, Global Address List, and domain-sg-Rooms), and only display the Custom Address Lists (domain-HK-AL and domain-sg-AL) — the ones shown in green in the photo?Proper whitelisting of microsoft.com on dnswl.org
I keep having the issue that system-generated e-mails, e.g. on Trace Reports get classified as spam by the receiving e-mail provider. The sender address is email address removed for privacy reasons and the e-mails go to my M365 mailbox and are redirected to my external monitoring mailbox with that e-mail provider. The e-mail provider calculates a score that includes checking the sender's IP address 52.101.69.91 with dnswl.org . Unfortunately, that address is only whitelisted for outlook.com and some secondary domains, but not for microsoft.com. Of course, the issue also occurs with mailto:email address removed for privacy reasons and other IP addresses, so this is an example. It started to occur around two weeks ago, not sure if the provider changed policies or Microsoft changed the whitelisting; of course the provider refuses to overrun dnswl.org it, e.g. by own whitelisting. Who at Microsoft could I ask to fix that kind of issues? I don't find any appropriate category in their support menues, M365 support says the cannot help (TrackingID#2603031420001611). Thanks in advance for any hints, this is my first posting here, so please forgive me, if this is a dumb question.
