Azure/Office 365 Graph API developer: RefreshToken, AccessToken, IdentityToken

These are 3 common terms (Refresh Token, Access Token, Identity Token) in Azure/Office 365 Graph API Cloud developer world and we get tons of queries on this. So let me try to explain them in simple terms … Access Token:- The access token is attached to every REST API request in the authorization header. -…


Office 365 Developer: Mail, Calendar, Contacts REST APIs and Hybrid Exchange

If you’re an Azure/Office 365 application developer, then this session is for you. In this Office 365 Developer session (as part of Redmond Interoperability Protocols Plugfest 2017), Deepak Singh, Program Manager, delivered presentation on Mail, Calendar, and Contacts REST APIs and Hybrid Exchange. Please make use of it.


Redmond Protocol Plugfest 2017

Dear fellow developers and quality assurance engineers / testers, please register/participate in our annual Redmond Interoperability Plugfest 2017. Register here Venue: Microsoft headquarters in Redmond, Washington Date: June 19-23, 2017 Detailed agenda: https://www.interopevents.com/redmond2017 – It’s designed to cover interoperability topics that span Microsoft, including Office, Windows, and SQL. There will be testing, workshops, and great…


Exploring with Microsoft Exchange Server Protocols docs

Recently I got requests from the developer community regarding my earlier article – so I take this opportunity to point how you can explore more about Microsoft Exchange Server Protocols. As you know through the Open Specifications program, Microsoft is helping developers open new opportunities by making technical documents related to interoperability for certain popular…


Registration starts – Redmond Interoperability Protocols Plugfest 2014!!

Microsoft-hosted protocol plugfests provide software developers with the opportunity to learn more about the Microsoft protocols and to test their implementations of the Microsoft Open Specifications. Hosted on the Microsoft Redmond campus, each plugfest focuses on a specific task or technology area. Presentations are conducted by Microsoft engineers, who are also available for one-on-one and…


Exchange Developer: Exchange Web Services – Best Practices (Part 2)

In Part 2, Matt discusses about searching, notifications, synchronization, and patterns when working with Exchange Web Services. The two part series would be good one for those who’re involved in building custom applications using Exchange development/Exchange Web Service. Enjoy!!


Exchange Developer: Exchange Web Services – Best Practices (Part 1)

Mid April, the Windows Server and Exchange Interoperability teams hosted an Open Specifications Plugfest event. The event was held in Redmond on the Microsoft campus for protocol developers implementing Exchange and Windows open specifications. I am planning to add couple of sessions related to Exchange and its developer… In this session, my peer Matt Stehle…


Office Developer: Microsoft Office 2010 Interactive Developer Map

Are you looking for Office 2010 Developer map? Here we go….The Microsoft Office 2010 Interactive Developer Map is a Silverlight application that helps developers visualize the different kinds of applications, services, client/server data-access technologies, on-premise servers, platform products and technologies, and tools that can help developers build multiple line-of-business solutions. The map provides links to…


Availability Web Service Protocol Specification References

Information for the availability service is provided via our open specifications document: [MS-OXWAVLS]. Information for the security model used in the availability service, please reference the following document: [MS-OXCPERM]. For more info, you can refer: Availability Web Services Protocol specification: http://msdn.microsoft.com/en-us/library/cc463891(v=exchg.80).aspx or http://download.microsoft.com/download/5/D/D/5DD33FDF-91F5-496D-9884-0A0B0EE698BB/[MS-OXWAVLS].pdf or http://download.microsoft.com/download/5/D/D/5DD33FDF-91F5-496D-9884-0A0B0EE698BB/Exchange_Protocols.zip.


Exchange Server Protocol docs

You can find the Microsoft Exchange Server 2010 SP1 RTM Protocol technical documentation set provides detailed technical specifications for Microsoft protocols and extensions to industry-standards or other published protocols that are implemented and used in Microsoft Exchange Server 2010 SP1 RTM. This allows the user to interoperate or communicate natively with Microsoft Office client and…


What you mean by Recommended vs. Supported vs. Deprecated vs. Deemphasized?

When we talk to customers they want to know what is the difference between Recommended, Supported, Deprecated and deemphasized means. This is already well explained in Patrick’s what unsupported mean article. In simple terms, “Recommended vs. Supported” means, Supported usually means well tested Support statements define strict boundaries Recommendations define the “best case” or the…


Documentation: Microsoft Exchange Server 2010 and Outlook Standards

Microsoft published the Microsoft Exchange Server 2010 and Outlook Standards documentation is intended for use in conjunction with publicly available standard specifications and network programming art, and assumes that the reader either is familiar with the aforementioned material or has immediate access to it. A protocol specification does not require the use of Microsoft programming…


Protocol documentation for Microsoft Exchange Server 2010 Beta

The Microsoft Exchange Server 2010 Protocol technical documentation set provides detailed technical specifications for Microsoft protocols and extensions to industry-standards or other published protocols that are implemented and used in Microsoft Exchange Server 2010. This allows the user to interoperate or communicate natively with Microsoft Office client and other server products. The documentation is designed…


Developer Messaging Best Practices : System.Net classes

Per the article, the following recommendations will help you use the classes contained in System.Net to their best advantage: Use WebRequest and WebResponse whenever possible instead of type casting to descendant classes. Applications that use WebRequest and WebResponse can take advantage of new Internet protocols without needing extensive code changes. When writing ASP.NET applications that…

1