Export (0) Print
Expand All

Preview Specifications

From time to time, Microsoft may publish a preview, or pre-release, version of an Open Specifications technical document for community review and feedback. To provide feedback for a preview version of a technical document, please follow the instructions for that document, if provided. Otherwise, you can provide feedback for a published technical document by using the Open Specification Forums.

The preview period for a technical document varies. Additionally, not every technical document will be published for preview.

After the preview period, the technical document is published to the appropriate location elsewhere in the Open Specifications MSDN Library for further reference.

This documentation contains detailed technical specifications for Microsoft protocols that are implemented and used by Exchange Server to interoperate or communicate with other Microsoft products. It also contains technical specifications for extensions to industry-standard and other published protocols that are used by Exchange Server. In addition, the documentation includes a set of companion overview and reference documents that supplement the technical specifications with conceptual background, overviews of inter-protocol relationships and interactions, and technical reference information.

Updated Protocol Documentation

The following documents were previously released and have been updated to include support for Office Desktop Client 2016 Preview products.

Specification

Description

[MS-OXABREF]: Address Book Name Service Provider Interface (NSPI) Referral Protocol

Specifies the Address Book Name Service Provider Interface (NSPI) Referral Protocol, which redirects client address book requests to an appropriate address book server.

[MS-OXBBODY]: Best Body Retrieval Algorithm

Specifies the Best Body Retrieval Algorithm, which provides a mechanism for efficient storage of message bodies.

[MS-OXCDATA]: Data Structures

Specifies common data structures that are used in remote operations.

[MS-OXCEXT]: Client Extension Message Object Protocol

Specifies the Client Extension Message Object Protocol, which allows clients to access mail app data stored in a mailbox.

[MS-OXCFOLD]: Folder Object Protocol

Specifies the Folder Object Protocol, which enables a client to create a folder and to manipulate an existing folder and its contents, which can include messages and subfolders.

[MS-OXCFXICS]: Bulk Data Transfer Protocol

Specifies the Bulk Data Transfer Protocol, which is responsible for the order and data flow that is used to transfer data between client and server.

[MS-OXCICAL]: iCalendar to Appointment Object Conversion Algorithm

Specifies the iCalendar to Appointment Object Conversion Algorithm, which converts between IETF RFC 2445, RFC 2446, and RFC 2447, and appointment and meeting objects.

[MS-OXCMAIL]: RFC 2822 and MIME to Email Object Conversion Algorithm

Specifies the RFC 2822 and MIME to Email Object Conversion Algorithm, which converts data from Internet standard email conventions to Message objects.

[MS-OXCMAPIHTTP]: Messaging Application Programming Interface (MAPI) Extensions for HTTP

Specifies the Messaging Application Programming Interface (MAPI) Extensions for HTTP, which enable a client to access personal messaging and directory data on a server by sending HTTP requests and receiving responses returned on the same HTTP connection. This protocol extends HTTP and HTTPS.

[MS-OXCMSG]: Message and Attachment Object Protocol

Specifies the Message and Attachment Object Protocol, which handles Message and Attachment objects.

[MS-OXCNOTIF]: Core Notifications Protocol

Specifies the Core Notifications Protocol, which handles notifications that are sent to a client when specific server events occur.

[MS-OXCPERM]: Exchange Access and Operation Permissions Protocol

Specifies the Exchange Access and Operation Permissions Protocol, which is used by clients to retrieve and manage the permissions on a folder.

[MS-OXCPRPT]: Property and Stream Object Protocol

Specifies the Property and Stream Object Protocol, which enables a client to read, set, and delete the properties of an object.

[MS-OXCROPS]: Remote Operations (ROP) List and Encoding Protocol

Specifies the Remote Operations (ROP) List and Encoding Protocol, which provides the remote operations used to access and modify mailbox information on the server.

[MS-OXCRPC]: Wire Format Protocol

Specifies the Wire Format Protocol, which serves as the transport basis for client/server communications over RPC.

[MS-OXCSPAM]: Spam Confidence Level Protocol

Specifies the Spam Confidence Level Protocol, which enables the handling of allow/block lists and the determination of junk email messages.

[MS-OXCSTOR]: Store Object Protocol

Specifies the Store Object Protocol, which is used by clients to log on to a user mailbox or public folders, read and write mailbox-level properties for that user mailbox, perform various housekeeping tasks for that mailbox, and determine the availability of content for public folders.

[MS-OXCTABL]: Table Object Protocol

Specifies the Table Object Protocol, which is used by a client to read and navigate through data that is retrieved in tabular format from the server.

[MS-OXDISCO]: Autodiscover HTTP Service Protocol

Specifies the Autodiscover HTTP Service Protocol, which extends the domain name system (DNS) and directory services to make the location and settings of mail servers available to clients.

[MS-OXDSCLI]: Autodiscover Publishing and Lookup Protocol

Specifies the Autodiscover Publishing and Lookup Protocol, which is used by clients to locate the Autodiscover HTTP service.

[MS-OXIMAP4]: Internet Message Access Protocol Version 4 (IMAP4) Extensions

Specifies extensions to Internet Message Access Protocol Version 4, which provide an authentication mechanism based on the NT LAN Manager (NTLM) Authentication Protocol, a delegate access mechanism to allow a delegate to access a delegator's mailbox, and support for the IMAP UIDPLUS extension described in [RFC4315].

[MS-OXLDAP]: Lightweight Directory Access Protocol (LDAP) Version 3 Extensions

Specifies extensions to Lightweight Directory Access Protocol (LDAP) Version 3, which enables directory access.

[MS-OXMSG]: Outlook Item (.msg) File Format

Specifies the .msg file format, which is used to represent individual email messages, appointments, contacts, tasks, and so on in the file system.

[MS-OXNSPI]: Exchange Server Name Service Provider Interface (NSPI) Protocol

Specifies the Microsoft Exchange Server implementation of the Name Service Provider Interface (NSPI) Protocol, which is used by Messaging API (MAPI) clients to access the directory service.

[MS-OXOAB]: Offline Address Book (OAB) File Format and Schema

Specifies the Offline Address Book (OAB) File Format and Schema, which is used for the local address book objects cache.

[MS-OXOABK]: Address Book Object Protocol

Specifies the Address Book Object Protocol, which defines the properties of various Address Book objects, and how the properties of Address Book objects interrelate.

[MS-OXOABKT]: Address Book User Interface Templates Protocol

Specifies the Address Book User Interface Templates Protocol, which defines the properties and operations that are permissible for address book templates.

[MS-OXOCAL]: Appointment and Meeting Object Protocol

Specifies the Appointment and Meeting Object Protocol, which extends the Message and Attachment Object Protocol for use with calendaring.

[MS-OXOCFG]: Configuration Information Protocol

Specifies the Configuration Information Protocol, which allows a client to share overlapping application settings with a server.

[MS-OXOCNTC]: Contact Object Protocol

Specifies the Contact Object Protocol, which enables the handling of contacts and personal distribution lists.

[MS-OXODLGT]: Delegate Access Configuration Protocol

Specifies the Delegate Access Configuration Protocol, which allows a user to delegate the responsibility for his or her mailbox to another user.

[MS-OXODOC]: Document Object Protocol

Specifies the Document Object Protocol, which enables representation of an ordinary file, such as a document generated by a word-processing application, in a mail folder for later retrieval. This protocol extends the Message and Attachment Object Protocol, which is described in [MS-OXCMSG].

[MS-OXOFLAG]: Informational Flagging Protocol

Specifies the Informational Flagging Protocol, which allows a Message object to be marked for either follow-up or categorization.

[MS-OXOJRNL]: Journal Object Protocol

Specifies the Journal Object Protocol, which is used to track activity related to a meeting, task, contact, or application file.

[MS-OXOMSG]: Email Object Protocol

Specifies the Email Object Protocol, which handles the representation of email messages in a messaging store.

[MS-OXONOTE]: Note Object Protocol

Specifies the Note Object Protocol, which enables the representation of a brief note that functions as the electronic equivalent of a paper sticky note.

[MS-OXOPOST]: Post Object Protocol

Specifies the Post Object Protocol, which enables the representation of a bulletin board post.

[MS-OXORMDR]: Reminder Settings Protocol

Specifies the Reminder Settings Protocol, which enables a user to discover and act upon appointments, tasks, messages, or contacts that have a deadline or for which follow-up is necessary.

[MS-OXORMMS]: Rights-Managed Email Object Protocol

Specifies the Rights-Managed Email Object Protocol, which is used by the client to create and consume a rights-managed email message.

[MS-OXORSS]: RSS Object Protocol

Specifies the RSS Object Protocol, which enables representation of an item that is from a news feed.

[MS-OXORULE]: Email Rules Protocol

Specifies the Email Rules Protocol, which manipulates incoming email messages on a server.

[MS-OXOSFLD]: Special Folders Protocol

Specifies the Special Folders Protocol, which specifies the default set of folders that an implementation supports, as well as other non-user-visible special folders for certain types of application data, such as reminders and views.

[MS-OXOSMIME]: S/MIME Email Object Algorithm

Specifies the S/MIME Email Object Algorithm, which handles the conversion of arbitrary clear-signed messages, and S/MIME opaque-signed and encrypted messages.

[MS-OXOSMMS]: Short Message Service (SMS) and Multimedia Messaging Service (MMS) Object Protocol

Specifies the Short Message Service (SMS) and Multimedia Messaging Service (MMS) Object Protocol, which enables clients and servers to create, modify, and delete SMS and MMS messages.

[MS-OXOSRCH]: Search Folder List Configuration Protocol

Specifies the Search Folder List Configuration Protocol, which enables a client to persist a user's search folders on the server. A search folder is a folder that is used to query for items that match specified criteria.

[MS-OXOTASK]: Task-Related Objects Protocol

Specifies the Task-Related Objects Protocol, which allows for the representation of task-related Message objects in a messaging store.

[MS-OXOUM]: Voice Mail and Fax Objects Protocol

Specifies the Voice Mail and Fax Objects Protocol, which enables servers to create and send Unified Messaging objects.

[MS-OXPHISH]: Phishing Warning Protocol

Specifies the Phishing Warning Protocol, which identifies and marks email messages that are designed to trick recipients into divulging sensitive information (such as passwords and/or other personal information) to a non-trustworthy source.

[MS-OXPOP3]: Post Office Protocol Version 3 (POP3) Extensions

Specifies extensions to Post Office Protocol Version 3 (POP3), which enable the listing and downloading of mail.

[MS-OXPROPS]: Exchange Server Protocols Master Property List

Specifies all properties used for communication between clients and servers, provides summary information about each property, and provides links to the documents in which the property value ranges and semantics are specified.

[MS-OXRTFCP]: Rich Text Format (RTF) Compression Algorithm

Specifies the Rich Text Format (RTF) Compression Algorithm, which compresses and decompresses RTF data to or from one of the supported compression formats.

[MS-OXRTFEX]: Rich Text Format (RTF) Extensions Algorithm

Specifies the Rich Text Format (RTF) Extensions Algorithm, which extends the RTF method of encoding by enabling the encapsulation of additional content formats (such as HTML) within the RTF body property of messages and attachments.

[MS-OXSHARE]: Sharing Message Object Protocol

Specifies the Sharing Message Object Protocol, which shares mailbox folders between clients.

[MS-OXSHRMSG]: Sharing Message Attachment Schema

Specifies the Sharing Message Attachment Schema, which defines the schema for an XML document used to establish a sharing relationship between two servers on behalf of client applications.

[MS-OXSMTP]: Simple Mail Transfer Protocol (SMTP) Extensions

Specifies extensions to the Simple Mail Transfer Protocol (SMTP) standards to facilitate authentication negotiation between a client and a server and to enable the server to close connections that exceed configured thresholds.

[MS-OXTNEF]: Transport Neutral Encapsulation Format (TNEF) Data Algorithm

Specifies the Transport Neutral Encapsulation Format (TNEF) Data Algorithm, which encodes and decodes Message and Attachment objects to an efficient stream representation.

[MS-OXWAVLS]: Availability Web Service Protocol

Specifies the Availability Web Service Protocol, which is used to request availability information for users and/or resources.

[MS-OXWCONFIG]: Web Service Configuration Protocol

Specifies Web Service Configuration Protocol, which is used to retrieve organization policy configuration information for a mailbox.

[MS-OXWMT]: Mail Tips Web Service Extensions

Specifies extensions to the Mail Tips Web Service Protocol, which retrieves mail tips for a mailbox.

[MS-OXWOAB]: Offline Address Book (OAB) Retrieval File Format

Specifies the Offline Address Book (OAB) Retrieval File Format, which delivers OAB data from server to client.

[MS-OXWOOF]: Out of Office (OOF) Web Service Protocol

Specifies the Out of Office (OOF) Web Service Protocol, which is used to configure server-based automatic email responses.

[MS-OXWSARCH]: Archiving Web Service Protocol

Specifies the Archiving Web Service Protocol, which enables clients to use a web service to archive items in a mailbox.

[MS-OXWSCEXT]: Client Extension Web Service Protocol

Specifies the Client Extension Web Service Protocol, which enables clients to use a web service to retrieve and disable client extensions.

[MS-OXWSCVTID]: Convert Item Identifier Web Service Protocol

Specifies the Convert Identifier Web Service Protocol, which enables a client to convert among the different identifier formats that can be used to locate items stored on the server.

[MS-OXWSGTRM]: Get Rooms List Web Service Protocol

Specifies the Get Rooms List Web Service Protocol, which provides a client with a list of locations of meeting rooms within the server organization. This protocol also provides a client with the list of meeting rooms within a selected location room list.

[MS-OXWSMSHR]: Folder Sharing Web Service Protocol

Specifies the Folder Sharing Web Service Protocol, which is responsible for managing Calendar folders that are shared between users in separate organizations.

[MS-OXWSSMBX]: Site Mailbox Web Service Protocol

Specifies the Site Mailbox Web Service Protocol, which enables clients to use a web service to set the lifecycle state of a site mailbox or unpin it from the client.

[MS-OXWUMS]: Voice Mail Settings Web Service Protocol

Specifies the Voice Mail Settings Web Service Protocol, which provides an extensibility point that enables clients to read and change information about Unified Messaging properties, play voice mail, or record greetings over the telephone.

[MS-PATCH]: LZX DELTA Compression and Decompression

Specifies LZX Delta compression, which is a derivative of the Microsoft Cabinet LZX format with some modifications to facilitate efficient delta compression.

[MS-XJRNL]: Journal Record Message File Format

Specifies the Journal Record Message File Format, which is used to format information about an email message that is sent through the server. The Journal Record Message File Format extends RFC 2045 and RFC 2046.

[MS-XLOGIN]: Simple Mail Transfer Protocol (SMTP) AUTH LOGIN Extension

Specifies the AUTH LOGIN extension to the SMTP Protocol, which supports a simple, base 64-encoded authentication mechanism.

Top of page

This documentation contains detailed technical specifications for file formats implemented in certain Office applications, including the binary file formats created by Word, Excel, and PowerPoint, and the Outlook Personal Folders (.pst) file format. In addition, the documentation includes a set of companion overview and reference documents that supplement the technical specifications with conceptual background and technical reference information.

Technical specifications for standards-based file formats implemented in Office applications may be found in the Standards Support section of the Open Specifications library.

Updated Protocol Documentation

The following documents were previously released and have been updated to include support for Office Desktop Client 2016 Preview products.

Specification

Description

[MS-OBPAS]: Office Broadcast Participant Service

The Office Broadcast Participant Service is used to join an existing broadcast session and transmit broadcast data to a protocol client from a protocol state server.

[MS-PWEDPS]: PowerPoint Web Editor Data Protocol

Specifies the PowerPoint Web Editor Data Protocol, which enables a protocol client to obtain information about and modify presentation content on a protocol server.

[MS-PWPHP]: PowerPoint Web Presentation Handler Protocol

The PowerPoint Web Presentation Handler Protocol is used by a protocol server to send presentation content to a protocol client.

[MS-PWVPDP]: PowerPoint Web Viewer Presentation Data Protocol

Specifies the PowerPoint Web Viewer Presentation Data Protocol, which enables a protocol client to obtain information about presentation content on a protocol server.

[MS-WOPI]: Web Application Open Platform Interface Protocol

Specifies the Web Application Open Platform Interface Protocol. This protocol identifies a set of operations that enables a client to access and change files stored by a server.

Top of page

This documentation contains detailed technical specifications for file formats implemented in certain Office applications, including the binary file formats created by Word, Excel, and PowerPoint, and the Outlook Personal Folders (.pst) file format. In addition, the documentation includes a set of companion overview and reference documents that supplement the technical specifications with conceptual background and technical reference information.

Updated Protocol Documentation

The following documents were previously released and have been updated to include support for Office Desktop Client 2016 Preview products.

Specification

Description

[MS-CTDOC]: Word Custom Toolbar Binary File Format

Specifies the Word Custom Toolbar Binary File Format, which contains data used by the structures that preserve toolbar customization. This protocol also specifies how toolbar customization provides a run-time solution for the creation and deployment of toolbar customizations that are specific to the content of a file.

[MS-CTXLS]: Excel Custom Toolbar Binary File Format

Specifies the Excel Custom Toolbar Binary File Format, which contains data used by the structures that preserve toolbar customization. This protocol also specifies how toolbar customization provides a run-time solution for the creation and deployment of toolbar customizations that are specific to the content of a file.

[MS-DOC]: Word (.doc) Binary File Format

Specifies the Word (.doc) Binary File Format, which is the binary file format used by Microsoft Word 97, Microsoft Word 2000, Microsoft Word 2002, and Microsoft Office Word 2003.

[MS-ODCFF]: Office Data Connection File Format

Specifies the Office Data Connection File Format, which is used for specifying data connection information that can be used to fetch data from a database.

[MS-ODRAW]: Office Drawing Binary File Format

Specifies the Office Drawing, or OfficeArt, binary file format. This file format exists as part of various Microsoft Office application binary file formats. The OfficeArt data represents the drawing elements and all their associated formatting in those Office applications. Typically these elements are represented as shapes contained within drawings or diagrams, but may include form controls or tables.

[MS-OFFCRYPTO]: Office Document Cryptography Structure

Specifies the Office Document Cryptography Structure, which is the file format for documents with Information Rights Management policies applied.

[MS-OFORMS]: Office Forms Binary File Formats

Specifies the Office Forms Binary File Format, which is the file format that applies to Office Forms. Office Forms are a collection of controls that can be embedded in client applications and stored as part of a file. Office Forms controls can be used to provide additional interactive surfaces, such as command buttons, check boxes, or option buttons, to the user. The client application provides the location and requests the type of persistence; the structure of the persistence is determined by Office Forms for binary formats and by the client application for text formats.

[MS-OGRAPH]: Office Graph Binary File Format

Specifies the Office Graph Binary File Format, which is the file format for embedded Microsoft Graph Chart objects that are commonly used by Microsoft Office 97, Microsoft Office XP, Microsoft Office 2003, and the 2007 Microsoft Office system documents.

[MS-ONESTORE]: OneNote Revision Store File Format

Specifies the OneNote Revision Store File Format (.one and .onetoc2). This file format is a collection of structures that specify a revision store organized into cross-referenced object spaces, containing objects with property sets, and containing a transaction log to ensure file integrity across asynchronous writes.

[MS-OSHARED]: Office Common Data Types and Objects Structures

Specifies the Office Common Data Types and Objects Structure, which are data types and data structures that are commonly used by Microsoft Office 97, Microsoft Office XP, Microsoft Office 2003, and the 2007 Microsoft Office system documents.

[MS-OVBA]: Office VBA File Format Structure

Specifies the Office VBA File Format Structure, which describes the Microsoft Visual Basic for Applications (VBA) File Format for Microsoft Office 97, Microsoft Office 2000, Microsoft Office XP, Microsoft Office 2003, and the 2007 Microsoft Office system. This specification also describes a storage that contains a VBA project, which contains embedded macros and custom forms for use in Office documents.

[MS-OWEMXML]: Office Web Extensibility Manifest Format

Specifies the Office Web Extensibility Manifest File Format, which provides the schema for Office Web Extension manifest files.

[MS-PPT]: PowerPoint (.ppt) Binary File Format

Specifies the PowerPoint (.ppt) Binary File Format, which is the binary file format used by Microsoft PowerPoint 97, Microsoft PowerPoint 2000, Microsoft PowerPoint 2002, and Microsoft Office PowerPoint 2003.

[MS-PST]: Outlook Personal Folders (.pst) File Format

Specifies the Outlook Personal Folders File Format, which provides the necessary technical information required to read and write the contents of a Personal Folders File. Each Personal Folders File represents a Message store that contains an arbitrary hierarchy of Folder objects, which contains Message objects, which can contain Attachment objects. Information about Folder objects, Message objects, and Attachment objects are stored in properties, which collectively contain all of the information about the particular item.

[MS-WORDLFF]: Word (.xml) Co-Authoring File Format in Document Lock Persistence Structure

Specifies the Word (.xml) Co-Authoring File Format in Document Lock Persistence Structure, which enables a protocol client to create and manage authors' presence within regions of a word processing document.

[MS-XLDM]: Spreadsheet Data Model File Format

Specifies the Spreadsheet Data Model File Format, which defines a binary file format that is used to store a portion of a tabular data model to represent tables, data, and relationships within a containing spreadsheet file format.

[MS-XLS]: Excel Binary File Format (.xls) Structure

Specifies the Excel Binary File Format (.xls) Structure, which is the binary file format used by Microsoft Excel 97, Microsoft Excel 2000, Microsoft Excel 2002, and Microsoft Office Excel 2003.

[MS-XLSB]: Excel (.xlsb) Binary File Format

Specifies the Excel (.xlsb) Binary File Format, which is a collection of records and structures that specify Excel workbook content. The content can include unstructured or semi-structured tables of numbers, text, or both numbers and text, formulas, external data connections, charts and images.

Top of page

This documentation contains detailed technical specifications for Microsoft protocols that are implemented and used by SharePoint Products and Technologies to interoperate or communicate with other Microsoft products. It also contains technical specifications for extensions to industry-standard and other published protocols that are used by SharePoint Products and Technologies. In addition, the documentation includes a set of companion overview and reference documents that supplement the technical specifications with conceptual background, overviews of inter-protocol relationships and interactions, and technical reference information.

Updated Protocol Documentation

The following documents were previously released and have been updated to include support for Office Desktop Client 2016 Preview products.

Specification

Description

[MS-BCSDPFFS]: Business Connectivity Services Deployment Package File Format

Specifies the Business Connectivity Services (BCS) Deployment Package File Format, which describes the contents of a deployment package for a BCS solution, the BCS-specific extensions to the Office Server ClickOnce application manifest, and a BCS-specific file format representing the properties of an external list.

[MS-BCSDWPS]: Business Connectivity Services Deployment Web Service Protocol

Specifies the Business Connectivity Services Deployment Web Service Protocol, which enables a protocol client to create a profile page for an external content type, retrieve solution package information for a collection of server objects, and assign a custom form to a server object.

[MS-BDCMFFS]: Business Data Connectivity Model File Format

Specifies Business Data Connectivity model Xml file format. The model file contains a collection of metadata objects describing line-of-business (LOB) systems in terms of LobSystem objects, LobSystem instances and the business data types they store as entities. This structure is typically consumed by a runtime engine that translates requests into a format understood by the native LOB system.

[MS-BDCRAWPS]: Business Data Connectivity Remote Administration Web Service Protocol

Specifies the Business Data Connectivity Remote Administration Web Service Protocol. This protocol enables protocol clients to create, store, and retrieve information about interfaces of line-of-business systems (LOB systems).

[MS-COPYS]: Copy Web Service Protocol

Specifies the Copy Web Service Protocol, which is used to copy files, including file metadata such as creation date and author, to one or more locations on a single protocol server or between different protocol servers.

[MS-CPSWS]: SharePoint Claim Provider Web Service Protocol

Specifies the SharePoint Claim Provider Web Service Protocol. This protocol enables a protocol client to access claims returned by the claim providers available on a protocol server. A typical scenario for this protocol is a client application that allows users to search and resolve users and groups from a set of directory services and external identity providers.

[MS-DWSS]: Document Workspace Web Service Protocol

Specifies the Document Workspace Web Service Protocol. This protocol is used to create, edit, and delete workspaces and folders for a SharePoint site configured as a Document Workspace.

[MS-ECTPWPS]: External Content Type Picker Web Service Protocol

Specifies the External Content Type Picker Web Service Protocol, which a protocol client uses to search and pick from external content types on a protocol server.

[MS-EMMWS]: Microsoft Enterprise Managed Metadata Web Service Protocol

Specifies the Enterprise Managed Metadata Web Service protocol, which enables a protocol client to interact with a managed metadata store. A typical scenario for using this protocol is tagging a document with managed metadata via a rich client application.

[MS-ESURL]: Excel Services Publishing Protocol

Specifies the Excel Services Publishing Protocol, which specifies how the protocol client should form the URL to the protocol server to display the contents of a published workbook in the browser.

[MS-FORMS]: Forms Service Protocol

Specifies the Forms Service protocol. This protocol enables a client to get a list of forms from a protocol server and to get individual forms from that list.

[MS-FSSHTTP]: File Synchronization via SOAP over HTTP Protocol

Specifies the File Synchronization via SOAP over HTTP Protocol, which enables one or more protocol clients to synchronize changes done on shared files stored on a server.

[MS-FSSHTTPB]: Binary Requests for File Synchronization via SOAP Protocol

Specifies the Binary Requests for File Synchronization via SOAP Protocol, which enables protocol clients to synchronize the state of a structured file hosted by a protocol server.

[MS-FSSHTTPD]: Binary Data Format for File Synchronization via SOAP

Specifies the MS-FSSHTTP schema for representing file data. This schema represents a traditional file, which is an array of bytes, efficiently in the MS-FSSHTTP storage model. A typical scenario for this schema is a client or server application transmitting a traditional file to or from an MS-FSSHTTP protocol server.

[MS-IMAGS]: Imaging Service Protocol

Specifies the Imaging Services Protocol, a set of client-server interactions that allows a client to retrieve, upload, and organize images on a server.

[MS-LISTSWS]: Lists Web Service Protocol

Specifies the Lists Web Service Protocol, which enables a protocol client to perform tasks related to list-based content on a protocol server.

[MS-MEETS]: Meetings Web Services Protocol

Specifies the Meetings Web Services Protocol, which provides methods to create and update Meeting Workspace sites.

[MS-METAWEB]: MetaWeblog Extensions Protocol

Specifies the MetaWeblog Extensions Protocol, which are a set of extensions to the MetaWeblog API to allow for more secure authentication mechanisms.

[MS-OFBA]: Office Forms Based Authentication Protocol

Specifies the Office Forms Based Authentication Protocol, which enables HTTP-based, forms authentication when other authentication mechanisms are not available.

[MS-OMS]: Office Mobile Service Protocol

Specifies the Office Mobile Service (OMS) Protocol. This protocol is used to transmit text and mobile messages between a protocol client and a protocol server.

[MS-OSALER]: Alerts Interoperability Protocol

Specifies the Alerts Interoperability Protocol, which is used to identify and interpret Internet messages that can be sent to protocol clients when a document, Web page or other type of resource is changed on a protocol server. This protocol also specifies the syntax and semantics of user-defined fields in message headers of those messages.

[MS-OSCO]: Office Server ClickOnce Manifest Structure

Specifies the Office Server ClickOnce Manifest Structure which contains runtime information specific to a Visual Studio Tools for Office solution.

[MS-OUTSPS]: Lists Client Sync Protocol

Specifies the Lists Client Sync Protocol, which allows clients to transfer data to and from a server that implements the Lists Web service.

[MS-PEOPS]: People Web Service Protocol

Specifies the People Web Service Protocol, which enables a protocol client to resolve and find principals. This protocol allows the protocol client to pass criteria, which consist of a list of keys and the principal type, to the protocol server and to receive back a list of resolved principals.

[MS-PERMS]: Permissions Web Service Protocol

Specifies the Permissions Web Service Protocol, which enables protocol clients to manage permissions to content items on the protocol server.

[MS-PLSP]: Published Links Web Service Protocol

Specifies the Published Links Web Service Protocol. This protocol specifies an operation that allows a protocol client to retrieve a list of potentially useful URLs and descriptive details about each URL.

[MS-SEARCH]: Search Protocol

Specifies the Search Protocol that enables clients to make queries against an Enterprise Search service, the protocol server responding with a list of items that are relevant to the search query. This protocol also allows protocol clients to request query suggestions for a given search query.

[MS-SHDACCWS]: Shared Access Web Service Protocol

Specifies the interface of the Shared Access Web Service protocol that is used for determining whether a document is being co-authored.

[MS-SLIDELI]: Slide Library Web Service Protocol

Specifies the Slide Library Web Service Protocol, which enables protocol clients to obtain information about slides in a slide library on protocol server.

[MS-SPAFWI]: SharePoint Activity Feed Web Interfaces Protocol

Specifies the SharePoint Activity Feed Web Interfaces Protocol, which specifies extensions for serializing and distributing social metadata about how the users of a Web site interact.

[MS-SPEMAWS]: SharePoint Email Web Service Protocol

Specifies the SharePoint E-Mail Web Service Protocol, which enables system administrators to manage information about contacts and groups of contacts that are controlled by certain directory services.

[MS-SPSTWS]: SharePoint Security Token Service Web Service Protocol

Specifies the SharePoint Security Token Service Web Service Protocol, which defines restrictions for several related protocols and enables interoperability and authentication with Web services that are provided by protocol servers.

[MS-STSSYN]: StsSync Data Structure

Specifies the StsSync Data Structure, which is a structure for encoding parameters necessary to connect to a remote list.

[MS-TMPLDISC]: Template Discovery Web Service Protocol

Specifies the Template Discovery Web Service Protocol. This protocol enables a protocol client to retrieve links to document templates that are associated with a document library on a protocol server.

[MS-UGS]: UserGroup Web Service Protocol

Specifies the UserGroup Web Service Protocol, which enables the definition, modification, and retrieval of information about users, groups, and roles.

[MS-UPSDWS]: User Profile Social Data Web Service Protocol

Specifies the User Profile Social Data Web Service Protocol, which is used to add, update, remove, and retrieve user-provided data that facilitates social networking. These data are in the form of tags, notes, and ratings about documents, Web pages, and other types of items that are stored on a protocol server.

[MS-USPSWS]: User Profile Service Web Service Protocol

Specifies the User Profile Service Web Service Protocol, which is a Web service to retrieve user profile data and data in common among users, as well as manage user profile properties, links, group memberships, and colleagues.

[MS-VERSS]: Versions Web Service Protocol

Specifies the Versions Web Service Protocol, which enables a protocol client to view and modify the version information for an existing file on a protocol server.

[MS-VGSFF]: Visio Graphics Service (.vdw) File Format

Specifies the Visio Graphics Service (.vdw) File Format. The file format specifies the streams and storages required to render a Web drawing, which is a collection of drawing pages, shapes, fonts, images, data connections, and diagram update information that can be rendered as a vector or raster drawing.

[MS-VIEWSS]: Views Web Service Protocol

Specifies the Views Web Service Protocol, which enables a protocol client to manage a list view.

[MS-VSDX]: Visio Graphics Service VSDX File Format

Specifies the Visio Graphics Service VSDX File Format. This file format identifies a Web Drawing, which is a collection of Drawing Pages, Masters, Shapes, Images, Comments, Data Connections, and recalculation information that can be rendered as a drawing.

[MS-WEBDAVE]: Web Distributed Authoring and Versioning Error Extensions Protocol

Specifies the Web Distributed Authoring and Versioning Error Extensions Protocol, which are the currently implemented extended error codes between WebDAV servers and WebDAV clients.

[MS-WEBSS]: Webs Web Service Protocol

Specifies the Webs Web Service Protocol, which provides methods for modifying SharePoint sites in the site collection.

[MS-WPPS]: Web Part Pages Web Service Protocol

Specifies the Web Part Pages Web Service Protocol, which enables a client to gather the information necessary to create browsable Web pages, and also uses server resources to create execution logic that reacts to changes in the server state.

[MS-WSSCAML]: Collaborative Application Markup Language (CAML) Structure

Specifies the Collaborative Application Markup Language (CAML) Structure, which are XML-based formats for queries, lists, and content types in Windows SharePoint Services, as used by other protocols.

[MS-WSSHP]: HTTP Windows SharePoint Services Headers Protocol

Specifies the HTTP Windows SharePoint Services Headers Protocol, which extends the Hypertext Transfer Protocol (HTTP) mechanisms to include new headers and messages that enable previously undefined behaviors, such as authenticating client connections, communicating error conditions, sending complex data, and interacting with information rights management systems, antivirus systems, and crawlers.

[MS-WSSREST]: ListData Data Service Protocol

Specifies the ListData Data Service Protocol, which specifies extensions to the Atom Publishing Protocol (AtomPub) and the Open Data Protocol (OData). The extensions specified in this document enable applications to expose list data, using common web technologies, as a data service that can be consumed by clients within corporate networks and across the Internet.

Top of page

Descriptions of and links to updated SQL Server protocol documents are provided below. To download any of the updated protocol documents, click the name of the desired specification listed in the table below. Previously released versions of SQL Server Protocol documentation are provided at SQL Server Protocols.

Updated Protocol Documentation

The following SQL Server protocol documents were previously released and have been updated. They contain revision marks for technical and document updates made since those documents were last published on May 20, 2014. Additions are shown in red, underlined text; deletions are shown in red, strikethrough text.

Specification

Description

[MS-CSDLBI-Diff]: Conceptual Schema Definition File Format with Business Intelligence Annotations

Specifies the structure and semantics of conceptual schema definition language (CSDL) annotations that are used in business intelligence (BI) applications.

[MS-RSWSRM2010-Diff]: Report Server Web Service for Report Management: ReportService2010

Specifies an API protocol that is provided by the ReportService2010 web service for managing objects and settings on a report server.

[MS-SCCSTR-Diff]: SqlClient Connection String Structure

Specifies a method for a Microsoft .NET Framework application to specify the parameters that are used to connect to a data source. This protocol can include one or more key/value pairs to specify information such as the user identification, the password, the server name, and the database name

[MS-SSAS-Diff]: SQL Server Analysis Services Protocol

Specifies the SQL Server Analysis Services Protocol, which provides methods for a client to communicate with and to perform operations on an analysis server.

Top of page

The following protocol documents contain descriptions of changes in protocol behavior associated with the Windows Technical Previews. To download a .zip file of all the new and updated protocol documents for the Windows Technical Previews, see the Windows Preview Protocols zip file.

Documentation for released versions of Windows was last updated on May 15, 2014, and is at Windows Protocols.

New Protocol Documentation

The following Windows protocol documents are new for the Windows Technical Previews.

Specification

Description

Last Published

[MS-HTTP2E-Preview]: Hypertext Transfer Protocol Version 2 (HTTP/2) Extension

This document specifies a profile of and an extension to the Hypertext Transfer Protocol (HTTP) version 2, which is defined by [IETFDRAFT-HTTP2].

The profile relaxes certain requirements of the base protocol in the interests of improved interoperability. The accompanying extension permits implementations to negotiate further relaxation when both sides agree.

April 2015

[MS-PKAP-Preview]: Public Key Authentication Protocol

Specifies the Public Key Authentication Protocol, which provides a method for HTTP clients to prove possession of a private key to a web server without having to rely on client Transport Layer Security (TLS) support from the underlying platform.

April 2015

[MS-RNAS-Preview]: Vendor-Specific RADIUS Attributes for Network Policy and Access Server (NPAS) Data Structure

Specifies the Vendor-Specific RADIUS Attributes for the Network Policy and Access Server (NPAS) Data Structure protocol, which describes the Microsoft RADIUS vendor-specific attributes (VSAs) that are implemented in the Windows operating system.

October 2014

[MS-SQOS-Preview]: Storage Quality of Service Protocol

Specifies the Storage Quality of Service (QoS) Protocol, which is a block-based protocol that is used to manage the Quality of Service configuration of I/O flows targeting remote files accessed over SMB3.

April 2015

[MS-WDHCE-Preview]: Wi-Fi Display Protocol: Hardware Cursor Extension

Specifies the Wi-Fi Display Protocol: Hardware Cursor Extension, which extends the Miracast v1.1 protocol to provide an additional, low-latency stream suitable for controlling the mouse cursor at a higher update rate.

October 2014

[MS-WFDPE-Preview]: Wi-Fi Display Protocol Extension

Specifies an extension for the Wi-Fi Display Technical Specification v1.1. Enables latency control, extended diagnostic information, and dynamic format changes on Wi-Fi Display Devices. When implemented, these extensions provide an improved and more consistent Wi-Fi Display experience for a variety of wireless display scenarios, including word processing, web browsing, gaming, and video projection.

April 2015

Note: MS-NCP-Preview: Network Controller Protocol has been removed.

Updated Protocol Documentation

The following Windows protocol documents were previously released and have been updated. They contain revision marks that show changes due to the Windows Technical Previews, as well as document updates made since those documents were last published on 5/15/2014. Additions are shown in red text; deletions are shown as strikethrough text.

Specification

Description

Last Published

[MC-DTCXA-Diff]: MSDTC Connection Manager: OleTx XA Protocol

Specifies the MSDTC Connection Manager: OleTx Transaction Protocol, which describes the extensions that support XA [XOPEN-DTP]-compliant software components in an OleTx distributed transaction processing environment.

New to this preview release, the lenDSN field in the XATMUSER_MTAG_RMOPEN message (section 2.2.3.2.5) supports a higher allowed value.

April 2015

[MS-ADA2-Diff]: Active Directory Schema Attributes M

Specifies the Active Directory Schema Attributes M, which contains a partial list of the objects that exist in the Active Directory schema (attributes beginning with M).

This document was updated as follows:

Several new attributes were added to the Active Directory schema.

Two of the new attributes are msDS-DeviceMDMStatus and msDS-ExternalDirectoryObjectId. These new attributes enable management of mobile device statuses and provide identifiers for users and groups when Windows Server operating system Active Directory is federated with Azure Active Directory.

Two of the new attributes are msDS-KeyCredentialLink and msDS-KeyCredentialLink-BL. These attributes contain key material and usage information.

The other new attributes are msDS-ComputerSID, msDS-CustomKeyInformation, msDS-DeviceDN, msDS-DeviceTrustType, msDS-IsCompliant, msDS-KeyApproximateLastLogonTimeStamp, msDS-KeyId, msDS-KeyMaterial, msDS-KeyPrincipal, msDS-KeyPrincipalBL, msDS-KeyUsage, and msDS-ShadowPrincipalSid. These attributes support the new Privileged Access Management optional feature.

April 2015

[MS-ADFSPIP-Diff]: Active Directory Federation Services Proxy and Web Application Proxy Integration Protocol

Specifies the Active Directory Federation Services and Proxy Integration Protocol. This protocol integrates Active Directory Federation Services with an authentication and application proxy to enable access to services located inside the boundaries of the corporate network for clients that are located outside of that boundary.

To support a future release of Windows, three new messages were added: Proxy Token Wrapper, Authentication Request, and Error Response. These messages are used by a new operation, Proxy Preauthentication for Active Clients, which is processed under the Application Proxy Runtime Behaviors for the server. The operation processes a request for authentication and returns a proxy token.

April 2015

[MS-ADSC-DIff]: Active Directory Schema Classes

Specifies the Active Directory Schema Classes, which contains a partial list of objects that exist in the Active Directory schema.

This document was updated as follows:

Attributes have been added to classes for mobile device management and federation identification and for the new Privileged Access Management optional feature. The msDS-ExternalDirectoryObjectId attribute was added to mayContain of the mailRecipient class. The msDS-DeviceMDMStatus, msDS-IsCompliant, msDS-DeviceTrustType, msDS-ComputerSID, and msDS-KeyCredentialLink attributes were added to systemMayContain of the msDS-Device class. The msDS-DeviceID attribute was added to the systemMayContain of the msDS-KeyCredential class.The msDS-CloudAnchor attribute was added to systemMayContain of the top class. The msDS-KeyPrincipalBL and msDS-KeyCredentialLink attributes were added to the systemMayContain of the user class.

Three new classes have been added for the new Privileged Access Management optional feature: Class msDS-KeyCredential, Class msDS-ShadowPrincipal, and Class msDS-ShadowPrincipalContainer.

April 2015

[MS-ADTS-Diff]: Active Directory Technical Specification

Specifies the core functionality of Active Directory. Active Directory extends and provides variations of the Lightweight Directory Access Protocol (LDAP).

This document was updated as follows:

Added the next behavior version identifier, DS_BEHAVIOR_WINTHRESHOLD, and the numerical values that are associated with it so that versioning can be handled properly. The following values have been added: the value 7 for domainControllerFunctionality, domainFunctionality, forestFunctionality, DC Functional Level (msDS-Behavior-Version), Domain NC Functional Level (msDS-Behavior-Version), and Forest Functional Level (msDS-Behavior-Version); the value 15.10 for Forest Revision; the value 2 for RODC Revision; the value 10.9 for Domain Revision.

Added information about the Privileged Access Management optional feature, which enables a link value to have an expiry time associated with it.

Added version numbers to the list of objectVersion values for the schema NC so that schema version can be handled properly: the schema version for AD DS is 80 and the schema version for AD LDS is 31.

April 2015

[MS-CMRP-Diff]: Failover Cluster: Management API (ClusAPI) Protocol

Specifies the Failover Cluster: Management API (ClusAPI) Protocol, an RPC–based protocol that is used to remotely manage a failover cluster. Managing a failover cluster involves managing the data that represents the configuration of the cluster, the entities that constitute the cluster, and the applications and services that run in a cluster. This protocol is also used to determine whether a computer system is currently acting as a member of a failover cluster and to control and query a service or application that is hosted by a failover cluster.

The ClusAPI protocol has been updated to include new structures and control codes to manage storage replication, determine if the cluster has the proper level of authorization to create an alternate computer object on a directory server, update the authentication token for cloud access, upgrade the operational version of the cluster, and retrieve values from the cluster registry.

April 2015

[MS-CRTD-Diff]: Certificate Templates Structure

Specifies the Certificate Templates Structure. This structure describes the syntax and interpretation of certificate templates, which forms the basis of certificate management for the Certificate Templates Protocol.

This document was updated as follows:

Changed the names of internal programming elements from "endorsement" to "hardware." This change supports a move to a more abstract model for key attestation.

January 2015

[MS-CSRA-Diff]: Certificate Services Remote Administration Protocol

Specifies the Certificate Services Remote Administration Protocol, which consists of a set of Distributed Component Object Model (DCOM) interfaces that enable administrative tools to configure the state and policy of a certification authority (CA) on a server.

This document was updated as follows:

Changed the names of internal programming elements from "endorsement" to "hardware." This change supports a move to a more abstract model for key attestation.

Changed the Windows version default value in the registry for DBSessionCount.

January 2015

[MS-DHCPM-Diff]: Microsoft Dynamic Host Configuration Protocol (DHCP) Server Management Protocol

Specifies the Microsoft Dynamic Host Configuration Protocol (DHCP) Server Management Protocol, which defines the RPC interfaces that provide methods for remotely accessing and administering the DHCP server. This protocol is a client and server protocol based on RPC that is used in the configuration, management, and monitoring of a DHCP server.

This protocol replaces earlier versions, to reflect the deprecation of the Network Access Protection feature, which is no longer supported in Windows versions after Windows 8.1 and Windows Server 2012 R2.

October 2014

[MS-DNSP-Diff]: Domain Name Service (DNS) Server Management Protocol -

Specifies the Domain Name Service (DNS) Server Management Protocol, which defines the RPC interfaces that provide methods for remotely accessing and administering a DNS server.

The DNS Server Management Protocol has been updated to support creating and managing a DNS Policy and a Client Subnet Record. New funtionality determines whether the DNS Policies configured on a DNS server are to be applied on DNS operations. Both DNS Policy and Client Subnet Records provide functionality to efficiently manage DNS operations. Added a new structure to specify a TLSA resource record [RFC6698].

April 2015

[MS-DRSR-Diff]: Directory Replication Service (DRS) Remote Protocol

Specifies the Directory Replication Service (DRS) Remote Protocol, an RPC protocol for replication and management of data in Active Directory.

Added support for the Privileged Access Management optional feature, including the enabling of the feature, verification of feature status, and a new DRS_MSG_GETCHGREPLY version with expiry-time support. The Privileged Access Management optional feature allows link values to have expiry times associated with them.

November 2014

[MS-DSCPM-Diff]: Desired State Configuration Pull Model Protocol

Specifies the Desired State Configuration Pull Model Protocol, which is used to get a client's configuration and modules from the server and to report the client's status back to the server.

The Desired State Configuration Pull Model Protocol has been updated to support the ability of the client to send status reports to the server as an HTTP POST request and to get status report details from the server.

April 2015

[MS-ECS-Diff]: Enterprise Client Sync protocol

Specifies the Enterprise Client Synchronization Protocol, which enables devices (such as tablets, PCs, or laptops) to synchronize files to and from a file server in a REST-based manner.

A new optional header has been added for detecting server changes. When the server receives this header it can wait to send a response until sync changes are complete or a timer threshold has been reached.

October 2014

[MS-EFSR-Diff]: Encrypting File System Remote (EFSRPC) Protocol

Specifies the Encrypting File System Remote Protocol, which is used to manage data objects stored in an encrypted form. The objective of encrypting data in this fashion is to enforce access control policies and to provide confidentiality from unauthorized users.

EFSRPC Metadata Version 3 has been added, providing the ability to convert a given object on the server to an encrypted state in the server's data store and to query the metadata about the encrypted object.

April 2015

[MS-FASP-Diff]: Firewall and Advanced Security Protocol

Specifies the Firewall and Advanced Security Protocol. The protocol manages firewall and advanced security components on remote computers.

Added one new policy version (0x0218), two flags, two new FW rule structures, and four new FW rule methods to enable processing of policy version 0x0218. The new programming elements added are the following: Flags (FW_RULE_FLAGS_MAX_V2_20 = 0x1000 and FW_RULE_FLAGS_LUA_CONDITIONAL_ACE = 0x1000), Structures (FW_NETWORK_NAMES and FW_RULE2_24, and Rules (RRPC_FWAddFirewallRule2_24, RRPC_FWSetFirewallRule2_24, RRPC_FWEnumFirewallRules2_24, and RRPC_FWQueryFirewallRules2_24).

October 2014

[MS-FSA-DIff]: File System Algorithms

Specifies File System Algorithms in terms of an abstract model for how an object store can be implemented to support the Server Message Block (SMB) Version 1.0 Protocol [MS-SMB] and the Server Message Block (SMB) Version 2.0 Protocol [MS-SMB2].

A new operation FSCTL_DUPLICATE_EXTENTS_TO_FILE has been added to make it look like a copy of a region from the source stream to the target stream has occurred when in reality no data is actually copied. This operation modifies the target stream’s extent list such that, the same clusters are pointed to by both the source and target streams’ extent lists for the region being copied.

October 2014

[MS-FSCC-Diff]: File System Control Codes

Specifies the File System Control Codes that define the network format of native Windows structures that may be used within other protocols.

A new File System Control (FSCTL) has been added to support the new FSCTL_DUPLICATE_EXTENTS_TO_FILE operation in [MS-FSA].

January 2015

[MS-GPAC-Diff]: Group Policy: Audit Configuration Extension

Specifies the Group Policy: Audit Configuration Extension, which provides a mechanism for an administrator to control audit policies on clients.

The Group Policy Audit Configuration Extension has been updated to include new audit subcategories that an administrator can choose to enable or disable in either a client system or per-user advanced audit policy. New SubcategoryGUIDs have been added to identify the additional audit subcategories.

January 2015

[MS-GPFAS-Diff]: Group Policy: Firewall and Advanced Security Data Structure

Specifies the Group Policy: Firewall and Advanced Security Data Structure extension, which provides a mechanism for an administrator to control the Firewall and Advanced Security behavior of the client. Updates to the protocol include two new token values for the Firewall Rules and the Firewall Rule Grammar Rule (section 2.2.2.19).

October 2014

[MS-GPPREF-Diff]: Group Policy: Preferences Extension Data Structure

Specifies the Group Policy: Preferences Extension Data Structure. This extension to the Group Policy: Core Protocol provides a mechanism to manage and deploy policy preferences.

The Group Policy: Preferences Extension Data Structure has been updated to include new FilterOs targeting criterion attributes for Windows vNext. Targeting criteria allow for a more granular selection of preferences beyond user or computer.

January 2015

[MS-IPAMM2-Diff]: IP Address Management (IPAM) Management Protocol Version 2

Specifies the IP Address Management (IPAM) Management Protocol Version 2. This protocol is used to remotely retrieve and manage the data in the IPAM data store. The IPAM data store consists of the data pertaining to the address space management, which includes the configuration data available with the DHCP and DNS server instances in the network.

The IPAM Management Protocol Version 2 has been updated to include enhanced DNS management capabilities. The updates enable implementers to manage DNS zones, DNS conditional forwarders, and resource records through the IPAM Management Protocol. The updates also provide an integrated view of IP address and DNS resource records. Modifications that support associating the DNS-related information with IP address objects are also included. The updates add cross-Active Directory forest support, which enables implementers to manage DC, DNS, and DHCP servers belonging to a different forest with a two-way trust relationship.

April 2015

[MS-KILE-Diff]: Kerberos Protocol Extensions

Specifies the Microsoft implementation of the Kerberos Protocol Extensions, as specified in [RFC4120], by specifying any Windows behaviors that differ from the Kerberos Protocol, in addition to Windows extensions for interactive logon and the inclusion of authorization information expressed as group memberships and related information.

Changed the processing associated with retrieval of information for portions of the KERB_VALIDATION_INFO structure. The processing now calls new procedures that have been defined in [MS-ADTS] to retrieve information about group memberships, including expiry times.

November 2014

[MS-LCID-Diff]: Windows Language Code Identifier (LCID) Reference

Describes localizable information in Windows. It lists all language code identifiers (LCIDs) available in all versions of Windows.

A number of new language tags have been added, along with further clarification as to when an LCID is, or is not, unique.

April 2015

[MS-LSAD-Diff]: Local Security Authority (Domain Policy) Remote Protocol

Specifies the Local Security Authority (Domain Policy) Remote Protocol. This protocol provides an RPC interface used for providing remote management for policy settings related to account objects, secret objects, trusted domain objects (TDOs), and other security-related policy settings.

This document was updated as follows:

Added new trust attributes, TRUST_ATTRIBUTE_CROSS_ORGANIZATION_NO_TGT_DELEGATION and TRUST_ATTRIBUTE_PIM_TRUST, to the LSAPR_TRUSTED_DOMAIN_INFORMATION_EX structure. This structure communicates the properties of a trusted domain; domain trusts are specified in [MS-ADTS] section 6.1.6.

January 2015

[MS-LWSSP-Diff]: Lightweight Web Services Security Profile

Specifies the Lightweight Web Services Security Profile. This profile specifies how to perform lightweight client authentication and security token exchange based on set of security-related Web services protocols.

Clarified the processing for Issuance Binding to express vNext handling of the "http://docs.oasis-open.org/ws-sx/ws-trust/200512/RSTRC/IssueFinal" action and the "http://docs.oasis-open.org/wssx/wstrust/200512/Bearer" and "http://docs.oasis-open.org/ws-sx/ws-trust/200512/Bearer" <KeyType> element values.

October 2014

[MS-MDE-Diff]: Mobile Device Enrollment Protocol

Specifies the Mobile Device Management Enrollment Protocol, which provides a mechanism for discovering devices and enrolling them into a management system. After enrollment, devices can be managed through the Microsoft Mobile Device Management Protocol [MS-MDM].

New material has been added to specify features supported by subsequent operating system releases.

April 2015

[MS-MDM-Diff]: Mobile Device Management Protocol

Specifies the Mobile Device Management Protocol (MDM), a subset of the Open Mobile Association (OMA) standard protocol, which provides a mechanism for managing devices previously enrolled into a management system through the Microsoft Mobile Device Management Enrollment Protocol [MS-MDE].

Multiple sections of this document have been revised to move informative content to an external repository, and further details of Transport behavior have been added.

April 2015

[MS-MWBF-Diff]: Microsoft Web Browser Federated Sign-On Protocol

Specifies the Microsoft Web Browser Federated Sign-On Protocol, which is primarily a restriction of the protocol that is specified in [WSFedPRP]. The restrictions are designed to enable greater interoperability by reducing the number of variations that must be implemented. This protocol also specifies minor additions to [WSFedPRP] to handle common scenarios.

Added support for two new query string parameters, domain_hint and prompt, which assist in the processing of a wsignin1.0 request message.

April 2015

[MS-NLMP-Diff]: NT LAN Manager (NTLM) Authentication Protocol

Specifies the NT LAN Manager (NTLM) Authentication Protocol, used in Windows for authentication between clients and servers. NTLM is used by application protocols to authenticate remote users and, optionally, to provide session security when requested by the application.

Added support for the WINDOWS_MAJOR_VERSION_10 value for the ProductMajorVersion field of the VERSION structure. Updated the Product Behavior note to specify values of ProductMajorVersion and ProductMinorVersion fields for different products.

January 2015

[MS-NRPC-Diff]: Netlogon Remote Protocol

Specifies the Netlogon Remote Protocol, an RPC interface that is used for user and machine authentication on domain-based networks; to replicate the user account database for operating systems earlier than Windows 2000 backup domain controllers; to maintain domain relationships from the members of a domain to the domain controller, among domain controllers for a domain, and between domain controllers across domains; and to discover and manage these relationships.

Added the next behavior-version identifier, DS_BEHAVIOR_WINTHRESHOLD, and the alphabetic flag value that is associated with it so that versioning can be handled properly; the bit value 'W' was added to the Flags field of the DsrGetDcNameEx2 method, along with a processing rule later in the same section.

October 2014

[MS-OAPX-Diff]: OAuth 2.0 Protocol Extensions

Specifies the OAuth 2.0 Protocol Extensions, which are used to extend the OAuth 2.0 Authorization Framework. These extensions enable authorization features such as resource specification, request identifiers, and login hints.

This document was updated as follows:

Added a new behavior version identifier, ad_fs_behavior_level, and the numerical values that are associated with it so that versioning can be handled properly.

Added the following components to support the new identifier:

  • five new normative references: [IETFDRAFT-JWK], [IETFDRAFT-JWT], [MS-WCCE], [OIDCCORE] and [RFC4559].

  • five additional, optional URI parameters: domain_hint, nonce, prompt, max_age, id_token_hint.

  • a new common data structures section that describes a set of optional POST body parameters: requested_token_use, assertion, resource - request and response, use_windows_client_authentication, csr, csr_type, x5c, which are used for communication between the client and the token endpoint.

Expanded the server’s abstract data model to define several new global fields: ad_fs_behavior_level, client_id, client_type, Windows_client_authentication_accounts, sign_certificates, jwks_ur.

Added detail information for all these components and their use in the server’s GET and POST operations, and in several new examples.

April 2015

[MS-PAC-Diff]: Privilege Attribute Certificate Data Structure

Specifies the Privilege Attribute Certificate Data Structure, which is used to encode authorization information. The Privilege Attribute Certificate also contains memberships, additional credential information, profile and policy information, and supporting security metadata.

This document was updated as follows:

Modified the Trust Boundary Type table used for authorization validation.

Added the ProtectedIdentityManagement (PIM) trust type that is used in SID Filtering by Active Directory. Processing details of this attribute can be found in [MS-ADTS] section 6.1.6.7.9.

January 2015

[MS-PSRDP-Diff]: PowerShell Remote Debugging Protocol

Specifies the PowerShell Remote Debugging Protocol (PSRDP), which extends the existing PowerShell Remoting Protocol (PSRP) specified in [MS-PSRP] to support debugging over a remote session.

Updates to the protocol include two new pipeline commands sent from the client to the server to set the server-side debugger stepping mode state and to set the server-side unhandled breakpoint mode state for processing unhandled breakpoints.

October 2014

[MS-PSRP-Diff]: PowerShell Remoting Protocol

Specifies the PowerShell Remoting Protocol, which is used by client applications to send pipelines of commands over a network for execution on a server.

The PowerShell Remoting Protocol has been updated to include the Information Record primitive type, which represents data from the pipeline.

April 2015

[MS-RA-Diff]: Remote Assistance Protocol

Specifies the Remote Assistance Protocol, which is used to facilitate basic connection, session initialization, file transfer, chat, share control, and VoIP control after a remote assistance connection is established.

The Remote Assistance Protocol has been updated to specify how the hashing algorithm is determined when encryption is selected for an RDP session.

April 2015

[MS-RAI-Diff]: Remote Assistance Initiation Protocol

Specifies the Remote Assistance Initiation Protocol, which is a set of Distributed Component Object Model (DCOM) interfaces for an authorized (expert) computer to initiate a Remote Assistance connection to another (novice) computer in a domain and to retrieve data required to connect an expert computer to a novice computer.

The Remote Assistance Initiation Protocol has been updated to include a new parameter for use when a Remote Assistance connection packet is an XML-formatted Unicode string.

April 2015

[MS-RDPBCGR-Diff]: Remote Desktop Protocol: Basic Connectivity and Graphics Remoting

Specifies the Remote Desktop Protocol: Basic Connectivity and Graphics Remoting, designed to facilitate user interaction with a remote computer system by transferring graphics display information from the remote computer to the user and transporting input from the user to the remote computer, where it may be injected locally.

Updates to this protocol include addition of values to version-related fields in the Server Core Data (TS_UD_SC_CORE) and Client Core Data (TS_UD_CS_CORE) data blocks.

April 2015

[MS-RDPEGFX-Diff]: Remote Desktop Protocol: Graphics Pipeline Extension

Specifies the Remote Desktop Protocol: Graphics Pipeline Extension, a graphics protocol that is used to encode graphics display data generated in a remote terminal server session so that the data can be sent from the server and received, decoded, and rendered by a compatible client.

Updates to this protocol include the addition of H.264 graphics extensions to support engineering workload scenarios.

January 2015

[MS-RDPEI-Diff]: Remote Desktop Protocol: Input Virtual Channel Extension

Specifies the Remote Desktop Protocol: Input Virtual Channel Extension, which is used to remote multitouch input frames from a terminal server client to a terminal server. Multitouch input frames are generated at the client, encoded, and sent to the server. Thereafter, these frames are received and decoded by the server and injected into the session associated with the remote user.

Updates to this protocol include the addition of pen remoting primitives to support client devices that allow stylus-based input.

January 2015

[MS-RDPERP-Diff]: Remote Desktop Protocol: Remote Programs Virtual Channel Extension

Specifies a Remote Desktop Protocol (RDP) feature that presents a remote application (running remotely on a remote application integrated locally (RAIL) server) as a local user application (running on the RAIL client machine).

Updates to this protocol include Z-order management enhancements to improve remote and local window layering and interaction.

January 2015

[MS-RPRN-Diff]: Print System Remote Protocol

Specifies the Print System Remote Protocol, which defines the communication of print job processing and print system management between a print client and a print server.

A port monitor action has been added for sending and receiving bidirectional data. The new action includes a data value that can be used by the port monitor when it is processing the data request. A new action has been added that specifies the minimum print client version required in order to connect to this printer.

April 2015

[MS-RSVD-Diff]: Remote Shared Virtual Disk Protocol

Specifies the Remote Shared Virtual Disk Protocol, which supports accessing and manipulating virtual disks stored as files on an SMB3 file server. This protocol enables opening, querying, administering, reserving, reading, and writing the virtual disk objects, providing for flexible access by single or multiple consumers. It also provides for forwarding of SCSI operations, to be processed by the remote virtual disk.

The Remote Shared Virtual Disk Protocol version 2 additionally enables a client application to create and manage snapshots of shared virtual disk files.

May 2015

[MS-SMB2-Diff]: Server Message Block (SMB) Protocol Versions 2 and 3

Specifies the Server Message Block (SMB) Protocol Versions 2 and 3, which support the sharing of file and print resources between machines and extend the concepts from the Server Message Block Protocol.

The SMB dialect numbering format has been revised. The new SMB 3.1.1 dialect allows for encryption and integrity algorithm selection to be negotiated, enhanced protection of negotiation and session establishment, enhanced error responses, and allows reconnects with a specified dialect.

April 2015

[MS-SSTP-Diff]: Secure Socket Tunneling Protocol (SSTP)

Specifies the Secure Socket Tunneling Protocol (SSTP), which is a mechanism to transport data-link layer (L2) frames on a Hypertext Transfer Protocol over Secure Sockets Layer (HTTPS) connection.

This protocol now supports the HTTPS Termination Proxy construct, which accepts HTTPS connections and passes on the decrypted HTTP payload. This feature is not supported in Windows Server 2012 R2, Windows Server 2012, or Windows Server 2008 R2.

October 2014

[MS-TDS-Diff]: Tabular Data Stream Protocol

Specifies the Tabular Data Stream Protocol, which facilitates interaction with a database server and provides for authentication and channel encryption negotiation; specification of requests in SQL (including Bulk Insert); invocation of a stored procedure, also known as a Remote Procedure Call (RPC); returning of data; and Transaction Manager Requests. It is an application layer request/response protocol.

This version introduces TDS protocol changes to enable the client to retrieve encryption metadata for columns encrypted in the database, so that the client can transparently encrypt query parameters and decrypt query results.

April 2015

[MS-TLSP-Diff]: Transport Layer Security (TLS) Profile

Specifies the Transport Layer Security (TLS) Profile, which is the authentication option to the Telnet protocol as a generic method for negotiating an authentication type and mode, including determining whether encryption should be used and whether credentials should be forwarded.

This document was updated as follows:

Added a new normative reference, [IETFDRAFT-TLSHASH-03], used in the negotiation of cipher suites and capabilities for Hello messages. The negotiation information in this reference is specific to the Windows platform.

January 2015

[MS-TPMVSC-Diff]: Trusted Platform Module (TPM) Virtual Smart Card Management Protocol

Specifies the DCOM Interfaces for Trusted Platform Module (TPM) Virtual Smart Card device management, which are used to manage virtual smart cards (VSCs) on a remote machine.

Updates to this specification document the ITpmVirtualSmartCardManager3 interface, which adds Smart Card Attestation to the ITpmVirtualSmartCardManager2 interface.

October 2014

[MS-TSGU-Diff]: Terminal Services Gateway Server Protocol

Specifies tunneling client-to-server traffic across firewalls when the Remote Desktop Gateway (RDG) server is deployed in the neutral zone of a network.

Updates to this protocol include the addition of the WebSocket protocol as a transport in order to support clients that do not allow outbound connections on nonstandard ports.

January 2015

[MS-WCCE-Diff]: Windows Client Certificate Enrollment Protocol

Specifies the Windows Client Certificate Enrollment Protocol, which consists of a set of DCOM interfaces that enable clients to request various services from a certification authority (CA). These services enable X.509 (as specified in [X509]) digital certificate enrollment, issuance, revocation, and property retrieval.

This document has been updated as follows:

Information has been added to define a second mode of key attestation. In addition to attestation using authority and subject, attestation using only the subject is now possible. This new mode of attestation can be more efficient than the existing mode of attestation.

January 2015

[MS-WCFESAN-Diff]: WCF-Based Encrypted Server Administration and Notification Protocol

Specifies the WCF-Based Encrypted Server Administration and Notification Protocol, which enables the protocol client to monitor and manage the protocol server in the same network. Updates to the protocol include the ability to retrieve a server's Azure Virtual Network settings and to use an address prefix to describe an IP address range in CIDR notation.

October 2014

[MS-WSUSAR-Diff]: Windows Server Update Services: Administrative API Remoting Protocol (WSUSAR)

Specifies the Windows Server Update Services: Administrative API Remoting Protocol (WSUSAR), which enables communication between the Windows Server Update Services (WSUS) management API and a WSUS server.

WSUSAR has been updated to include dynamic category functionality for WSDL operations in WSUS. A dynamic category represents a property, such as a device or device model, that is shared by a number of connected client computers. A server implementation can track a dynamic category to more effectively filter the number of updates that need to be synchronized using the Windows Update Services: Server-Server Protocol [MS-WSUSSS]. This update provides support for managing dynamic categories.

January 2015

[MS-WSUSSS-Diff]: Windows Update Services: Server-Server Protocol

Specifies the Windows Update Services: Server-Server Protocol, which enables a hierarchically organized collection of servers to synchronize metadata and content associated with software updates over the Internet by using SOAP and HTTP protocols.

The Windows Update Services: Server-Server Protocol has been updated to add support for using Windows Update Services to update new and revised hardware and software drivers.

April 2015

[MS-WUSP-Diff]: Windows Update Services: Client-Server Protocol

Specifies the client-to-server protocol for Windows Update Services. The protocol enables client computers to determine available, applicable software updates, and to download those updates for installation over the Internet using SOAP and HTTP protocols.

The Windows Update Services: Client-Server Protocol has been updated to add new fields to the RegisterComputer method to enable mobile device registration.

April 2015

Top of page

This documentation contains detailed technical documents for the Open Document Format (ODF) and Open XML (ECMA-376 and ISO/IEC-29500) file formats implemented in Word, Excel, and PowerPoint.

Updated Protocol Documentation

The following documents were previously released and have been updated to include support for Office Desktop Client 2016 Preview products.

Specification

Description

[MS-CUSTOMUI]: Custom UI XML Markup Specification

Specifies the Custom UI XML Markup specification, which contains information about how the 2007 Microsoft Office system implements UI customization in the context of ECMA-376 Office Open XML File Formats [ECMA-376].

[MS-CUSTOMUI2]: Custom UI XML Markup Version 2 Specification

Specifies the Custom UI XML Markup, which is used to implement UI customization in the context of the standards for Microsoft Office Open XML file formats as specified in ISO/IEC29500:2012.

[MS-DOCX]: Word Extensions to the Office Open XML (.docx) File Format

Specifies the Word Extensions to the Office Open XML File Format, which includes elements and attributes that extend the XML vocabulary for representing word processing documents as presented in the ISO/IEC-29500 specification.

[MS-ODRAWXML]: Office Drawing Extensions to Office Open XML Structure

Specifies extensions to the DrawingML OOXML File Format Structure, which is used in WordprocessingML, SpreadsheetML and PresentationML documents.

[MS-OFFMACRO2]: Office Macro-Enabled File Format Version 2

Specifies the structures of macro-enabled WordprocessingML, SpreadsheetML, and PresentationML file formats that are either not present in or modified from non-macro-enabled WordprocessingML, SpreadsheetML, and PresentationML file formats.

[MS-OWEXML]: Office Web Extensibility Extensions to Office Open XML Structure Specification

Specifies the Office Web Extensibility Extensions to Office Open XML File Format, which shows the elements and attributes that extend the XML vocabulary for representing Office Web Extensions.

[MS-PPTX]: PowerPoint (.pptx) Extensions to the Office Open XML File Format

Specifies elements and attributes that extend the XML vocabulary for representing PresentationML documents described in ISO/IEC-29500 specification.

[MS-XLSX]: Excel (.xlsx) Extensions to the Office Open XML SpreadsheetML File Format

Specifies the Excel (.xlsx) Extensions to the Office Open XML SpreadsheetML File Format, which are extensions to the Office Open XML file formats as described in [ISO/IEC-29500-1]. The extensions are specified using conventions provided by the Office Open XML file formats as described in [ISO/IEC-29500-3].

Top of page

Show:
© 2015 Microsoft