Microsoft Signals the End for Exchange Web Services
On September 19, 2023 Microsoft announced their intention to retire the Exchange Web Services API on 1 October 2026. The suggested replacement is the Microsoft Graph API. Microsoft acknowledges that some gaps exist that they need to close before EWS retirement happens, but one big issue they didn’t discuss is what happens to the backup products that currently use EWS to backup Exchange Online. https://office365itpros.com/2023/09/20/exchange-web-services-retire/
Teams uses EWS-API wrong which leads to wrong timezone in meetings
Hi, we do have an Exchange Hybrid Setup. On-Prem we do use OWA only. No Outlook-Client. When a user creates a Teams meeting (inside the Teams calendar) they sometimes use OWA when changing the meeting for comfort reasons (drag&drop). Here the problems begin. A little example: - User sets up meeting at 11:00 a.m. within the Teams calendar. - User changes meeting to 9:00 a.m. via OWA on the Exchange on-prem - Within in the organisation, everything is OK. But every External now has the appointment at 1:00 p.m. So somehow Exchange does a +2h (summertime maybe involved) to the orginal starting time of the meeting. But just for external participants. Inside the organisation everything is fine. Exchange always does the +2h based from the original meeting starttime. So moving the appointment to 3:00 p.m. will also lead to 1 p.m. for the External. Technically the .ics gets changed from "W. Europe Standard Time" to "UTC". If we change the meeting in the Teams calendar, everything is fine. If you create the meeting On-Prem and change it On-Prem or in the Teams calendar, everything is fine. It is just Online created meetings, changed On-Prem what causes the issue. I attached a screenshot of the .ics file. Right side shows the original meeting from Teams. Left side shows the changes of the meeting after leaving Exchange On-Prem. Does anybody have an idea where to look? Cheers SebastianUpdating unattended EWS scripts using modern auth
Hi there, a lot of possibilities about phasing out legacy authentication have been discussed here. But I still have a lack of information or let's say I want to find the most comfortable and most secure possibility for my customers. Step-by-Step guide guide for powershell usage even unattended, but only in EXO V2 module But if your scripts contain EWS connections you have to initialize a different way of authentication. So I found the following option using MSAL, unfortunately this does not work in unattended mode. Connect EWS API with Modern Authentication using PowerShell And then there is the possibility using the secure application model. Secure application model I got this working now, the creation of the token for the first time has to be done interactively and the token only lasts for 90 days. I read the hint for securely saving the token to the Azure KeyVault, but how do I do this and how can I re-call this token? Is there even a better way of refreshing the token manually? Is this now the new go-to solution for unattended EWS scripts, or do you have a even better solution?
Cannot Get EmailMessage Name to Display in Sent Emails Using EWS
Hi, I cannot set EmailMessage.Name to display a custom name in emails sent via Microsoft.Exchange.WebServices.Data 2.2 (assembly v15). Is it being overridden by Exchange, using the email account's Name? I've tried all possible ways, even the "display name<email-address>" format, nothing seems to work. Thanks. // Example var senderEmailAddress = new EmailAddress("myemail@blah.com") { Name = "My Name" }; // Or senderEmailAddress = new EmailAddress("My Name <myemail@blah.com>") // Or... etc. tried many diff. ways, nothing works. :( var message = new EmailMessage(exchangeService) { Sender = senderEmailAddress, Body = new MessageBody(BodyType.HTML, "test"), Subject = "test" }; message.SendAndSaveCopy(WellKnownFolderName.SentItems);
Exchange Web Services - Admin Account but without License
Hi, Is there a way to call the Exchange Web Services using an unlicensed Exchange Administrator account [unlicensedexchangeadmin@test.com] to list all public folders? Scenario: Listing Public Folders 1. Using the Exchange Admin Center with the unlicensed Exchange Administrator account, I can list the public folders. 2. Using the EWS.GetFolder with the same credentials, ErrorNonExistentMailbox was returned and no folders were listed. Thanks, Christle
