Skip to main content

Office UI licensing for developers

Overview

The Office UI licensing program is designed for software developers who wish to implement the Office UI as a software component and/or incorporate the Office UI into their own applications.

A license to use the Microsoft-claimed intellectual property in the Office UI is required when the software developer does not use one of the Microsoft-provided implementations of the UI that carries a separate license (currently either the Microsoft Windows 7 API implementation or the Microsoft WPF implementation in the .NET framework 4).

A license is also required when the software developer wishes to use elements of the Office 2010 UI that are not provided by those other implementations.

How to implement the Office UI in your own software

There are currently three primary categories of ways for a software developer to implement the Office UI in their own application or component.

 Use the Microsoft Windows 7 Scenic Ribbon implementation
Details about the Scenic Ribbon can be found on the MSDN Code Gallery. Use of the Scenic Ribbon implementation is governed by the Microsoft Windows SDK EULA and does not require a developer to accept the terms of the Office UI license on this site.
 
 Use the Microsoft Ribbon for WPF Implementation
Details about the Microsoft Ribbon for WPF Implementation (delivered via MS Downloads) can be found in the MSDN Library. Use of the Microsoft Ribbon for WPF is governed by a EULA similar to that of the .NET Framework. This release does not require developers to accept the terms of the Office UI license on this site.
 
 

Use Microsoft Foundation Classes (MFC) Ribbon, build it yourself, or use a
third-party component

All of the options in this category require acceptance of the Office UI License terms on this site. The additional benefits of this category include the ability to implement across more platforms, the ability to use elements of the Office 2010 UI that are not incorporated in the other implementations, and the ability to use a third-party component that may have other benefits to you as a developer.

If you find this category appropriate you should read the materials on this site, specifically the Office UI License and the Office UI Design Guidelines. You may search the web for component vendors by searching for terms like "Microsoft Ribbon component vendor".

Evaluate prior to licensing the Office UI

Accept the license terms for the Office UI

  • License the Office UI

    Visit this site and accept a simple click-through agreement to officially license the Office UI for use in your own products.

Related sites

  • Office Fluent UI for developers

    Find developer resources for customizing the Backstage view for Office 2010 and the Ribbon UI for Office 2010 and the 2007 Office system.