On Premise
3 TopicsHow to Delete a Composing Email Attachment via Outlook Add-in?
Context: Server: Exchange Server 2019 on premise Client: OWA Category: Outlook Add-in Office JS API Set: Supported up to 1.5 only Problem Details: Delete an attachment added manually or through EWS API to an email item. Limitations: 1. Limitation of makeEWSRequestAsync() Office JS method: The makeEWSRequestAsync method in Office.js does not support the DeleteAttachment SOAP operation, which is required from outlook add in. -> Attempted Workaround - Using fetch with EWS SOAP Request: I tried invoking the DeleteAttachment operation via a fetch call to the EWS endpoint. However, EWS response states "requested web method is not allowed for this application". 2. OWA Limitation: As OWA in this environment only supports Office.js up to version 1.5, the modern attachment Office JS APIs and Graph APIs are not an option. Question: In an Exchange On-Premises scenario, how can I programmatically delete attachments via my add-in? Specifically, is there a recommended approach to obtain a valid token for EWS requests, or any supported alternative to perform DeleteAttachment? Any way to convert EWS attachment ID to Office JS attachment UUID? Additional Notes: I am aware that Exchange Online supports more modern APIs (Graph/REST), but my current deployment is strictly Exchange On-Premises. The add-in works well for reading attachments and other operations, except for deletion. Any guidance or recommendations would be highly appreciated! Thank you in advance.112Views0likes1CommentExchange 2019 On Premise 2FA activation only for some mailboxes users
Hi ! We have an AD Forest with Exchange 2019 containing multiple MBX and CAS Server with multiple DAG as a Hosted Exchange for our customers. We want to enable 2FA on one of our client's hosted domains. Apparently we can activate it on all CAS for all mailboxes but not only for some. We have tested activating 2FA with ADFS on two CAS servers and it works. Now we want to restrict users using 2FA to only use these two CASs and block access on CASs that do not have 2FA enabled. Because otherwise it is possible to log in via the other CASs on their mailboxes. Does anyone have a solution to do this? I tried to do it with Exchange 2019 new-clientaccessrule commands but it is not possible with Exchange 2019 On Premise servers, some parameters like ExceptAnyOfAuthenticationTypes are not available. We also considered doing: - A second Exchange organization in the same forest (this is not possible).- A second forest with other Exchange servers (new organization) but this involves a lot of servers in our case. Thanks for your advice and help!566Views0likes0CommentsGraph API access to Exchange Server 2019 hybrid setup (on prem mailbox)
I read within the Microsoft docs (https://docs.microsoft.com/en-us/graph/hybrid-rest-support) that it should be possible to access basic resources like calendar or mail via the Graph API. Behind the scenes, when Microsoft Graph identifies that a REST API call is attempting to access an on-premises mailbox in a hybrid deployment, it proxies the REST request to an on-premises REST endpoint which then processes the request. This discovery makes accessing the REST API possible. We are using a hybrid setup with Exchange Server 2019 and on Prem mailboxes, but unfortunately I'm not able to access any data from there via Graph API.4.3KViews1like1Comment