Have an Exchange 2016 environment that has both internal and external access, specifically having separate FQDNs for the EWS internal and external URL in the virtual folder's configuration.I have seen this in a live production environment but have not been able to setup my lab correctly so far to attempt to reproduce. Other calls appear to go correctly to the external URL and the property returns the external URL as expected. When using getCallbackTokenAsync from an Outlook on Windows client while external to the Exchange environment, the command is sent through the internal EWS URL (as seen through Fiddler) when the client is not on the internal network. It is expected that the client/Office Add-ins framework would use the appropriate URL depending on the client's network status (External vs Internal access). When using getCallbackTokenAsync from an Outlook on Windows client while external to the Exchange environment, the command is sent through the external EWS URL (as seen in fiddler).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |