exchange-server-2016

MS Graph API return errors for Hybrid integration only on some IPs

由 不打扰是莪最后的温柔 提交于 2021-02-08 03:27:26
问题 We have an application that uses MS Graph API to integrate with our customer's email/calendar. One of the customers (Customer A) with the Hybrid setup, have reported issues. All the users suddenly got email integration not working. We have performed a couple of testing calls (endpoint /me/sendMail) to MS Graph API using our production app credential and different environments (local, dev cloud AWS, staging cloud GCP, prod cloud GCP) and valid user tokens. Here are the results and strange

MS Graph API return errors for Hybrid integration only on some IPs

由 ╄→гoц情女王★ 提交于 2021-02-08 03:27:15
问题 We have an application that uses MS Graph API to integrate with our customer's email/calendar. One of the customers (Customer A) with the Hybrid setup, have reported issues. All the users suddenly got email integration not working. We have performed a couple of testing calls (endpoint /me/sendMail) to MS Graph API using our production app credential and different environments (local, dev cloud AWS, staging cloud GCP, prod cloud GCP) and valid user tokens. Here are the results and strange

MS Graph API return errors for Hybrid integration only on some IPs

由 主宰稳场 提交于 2021-02-08 03:27:09
问题 We have an application that uses MS Graph API to integrate with our customer's email/calendar. One of the customers (Customer A) with the Hybrid setup, have reported issues. All the users suddenly got email integration not working. We have performed a couple of testing calls (endpoint /me/sendMail) to MS Graph API using our production app credential and different environments (local, dev cloud AWS, staging cloud GCP, prod cloud GCP) and valid user tokens. Here are the results and strange

A fatal error occurred while creating a TLS client credential. The internal error state is 10013

由 假如想象 提交于 2020-05-25 09:02:31
问题 Recently deployed a Windows 2016 Standard Server, with Active Directory and Exchange 2016. We have disabled SSL 1.0, 2.0 and 3.0 for both Server and Client, and have disabled TLS 1.0 and TLS 1.1. We are repeatedly getting the following entry in our system log. What is causing this, and how can I fix it. 回答1: Basically we had to enable TLS 1.2 for .NET 4.x . Making this registry changed worked for me, and stopped the event log filling up with the Schannel error. More information on the answer

A fatal error occurred while creating a TLS client credential. The internal error state is 10013

由 独自空忆成欢 提交于 2020-05-25 09:01:29
问题 Recently deployed a Windows 2016 Standard Server, with Active Directory and Exchange 2016. We have disabled SSL 1.0, 2.0 and 3.0 for both Server and Client, and have disabled TLS 1.0 and TLS 1.1. We are repeatedly getting the following entry in our system log. What is causing this, and how can I fix it. 回答1: Basically we had to enable TLS 1.2 for .NET 4.x . Making this registry changed worked for me, and stopped the event log filling up with the Schannel error. More information on the answer

Microsoft Graph API : Restrict scope of calendar.readWrite and Audit mailbox access by Application Permission

由 风流意气都作罢 提交于 2020-01-25 00:26:07
问题 We are using AD deployed Daemon applications that have full read/write access to user's calendar in office 365 to get meeting notifications from Graph API. We have moved away from EWS because of constant issues and MS depreciating its use. There does not currently seem to be a way of restricting the scope of Office 365 Calendar.ReadWrite permission from the organization level to a group/user. Fortune 500 customers are worried that our application has access to all sensitive data inside their

Can we connect to Exchange 2016 using EWS Managed API?

由 删除回忆录丶 提交于 2019-12-05 21:09:49
问题 I am using EWS Managed API 2.2 and it does not show the Exchange version 2016 in its enumeration. I can see the versions upto Exchange 2013. So how can I connect to Exchange Server 2016? Is the API, yet to be updated from Microsoft or do I need to use any other API's to connect to Exchange 2016 ? 回答1: It will connect just fine. You don't need to set the version to match the server, you set the version to indicate the lowest level of service you support. 来源： https://stackoverflow.com/questions

Does Exchange Server (in-house) suppport REST API?

由 倾然丶 夕夏残阳落幕 提交于 2019-12-04 12:14:17
问题 This document that applies to Exchange Server suggests that the bulk of API / Web Services is SOAP based: https://msdn.microsoft.com/en-us/library/office/dd877012(v=exchg.150).aspx However i see that Office 365 (which i assume is cloud based) supports a REST API. https://msdn.microsoft.com/en-us/library/office/dn776319(v=exchg.150).aspx But there it says that this documentation applies to Exchange Online / Office 365 only. So if i have an in-house Exchange Server, will it also support REST?

Can we connect to Exchange 2016 using EWS Managed API?

由 自闭症网瘾萝莉.ら 提交于 2019-12-04 03:35:02
I am using EWS Managed API 2.2 and it does not show the Exchange version 2016 in its enumeration. I can see the versions upto Exchange 2013. So how can I connect to Exchange Server 2016? Is the API, yet to be updated from Microsoft or do I need to use any other API's to connect to Exchange 2016 ? It will connect just fine. You don't need to set the version to match the server, you set the version to indicate the lowest level of service you support. 来源： https://stackoverflow.com/questions/34774101/can-we-connect-to-exchange-2016-using-ews-managed-api

Name of Version property in ServerVersionInfo element for Exchange Server 2016?

由 有些话、适合烂在心里 提交于 2019-12-01 20:57:16
问题 With Exchange Server 2016 being available for some time (as of 15. March it's at 2016 CU1), I want to properly detect the Version that gets returned in the SOAP header of each Exchange Web Services response message: <ServerVersionInfo MajorVersion="" MinorVersion="" MajorBuildNumber="" MinorBuildNumber="" Version="" /> The latest schema version mentioned in e.g. the 'EWS schema versions in Exchange' page is Exchange2013_SP1 . What is the name returned for Exchange 2016? I do not yet have an
订阅 exchange-server-2016