What is the status of Microsoft &quot;ribbon&quot; licensing as of 2017?
<p>In 2007, the <a href="https://en.wikipedia.org/wiki/Ribbon_(computing)" rel="noreferrer">"fluent UI" or ribbon</a> had IP rights asserted and <a href="https://blogs.msdn.microsoft.com/jensenh/2006/11/21/licensing-the-2007-microsoft-office-user-interface/" rel="noreferrer">required a license</a> from Microsoft. That license is now <a href="https://msdn.microsoft.com/en-gb/office/aa973809.aspx" rel="noreferrer">no longer available</a>, the page only stating 'retired'.</p>

<p>What is the status of using a ribbon UI on Windows or any other platform? Is Microsoft still asserting IP rights, and is a license required?</p>

<p>Note that there are many questions online about this, but no answer, much less a sourced one stating Microsoft's official position. This leaves many developers in a state of uncertainty.</p>

<hr>

<p>As of 2017:</p>

<ul>
<li>No documentation on MSDN <em>anywhere</em> mentions a license.  Consider, for example, the <a href="https://docs.microsoft.com/en-gb/cpp/mfc/reference/cmfcribbonbar-class" rel="noreferrer">MFC ribbon overview</a>.</li>
<li>The VC++ 2017 MFC <code>CMFCRibbonBar</code> class, the only ribbon installed with VS2017, links to the retired license in its header. This header has not changed for many years. Its documentation does not mention a license.</li>
<li>The Visual Studio 2017 license does not mention the ribbon.</li>
<li>The Windows 10 SDK license does not mention the ribbon (checked against 10.0.15603.137, downloaded 2017-04-11.)</li>
<li>Some believe this means <a href="https://community.embarcadero.com/blogs/entry/ribbon-controls-in-rad-studio-10-1-berlin" rel="noreferrer">no-one who did not sign a license before it was retired are able to legally use a ribbon</a>.</li>
<li>A 2009 comment in a forum (not a good basis) states there are <a href="https://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/b43aa9cc-0aac-44b5-afb9-af66a9997225/what-is-the-windows-ribbon-license?forum=windowsribbondevelopment" rel="noreferrer">"no unusual licensing requirements"</a>.</li>
<li>There has been no statement by Microsoft of a change in its attitude the the ribbon, arguably meaning that now a license is no longer available, no developers can use a ribbon.</li>
<li>Microsoft uses a ribbon in its macOS Office applications, but has not indicated if other developers may use a ribbon on non-Windows platforms</li>
<li>There is significant doubt <a href="https://en.wikipedia.org/wiki/Ribbon_(computing)#Patent_controversy" rel="noreferrer">if the ribbon is valid IP</a>.</li>
</ul>

<p>This leaves all developers who did not sign a license prior to it being retired in limbo and uncertainty, not knowing:</p>

<ul>
<li>If they can use the inbuilt WinAPI ribbon control on Windows 10 without a license</li>
<li>If they can use a third party ribbon control on Windows without a license</li>
<li>If they can use a third party ribbon control on macOS or Linux</li>
<li>If they can use a ribbon for an application that competes with a Microsoft application (either Office, or other.)</li>
</ul>

<blockquote>
  <p>Please cite sources, and prefer the kind of sources you could quote if
  it became legally important, above sources that are a comment on a forum. I'm seeking a
  definitive answer, and won't mark a "it's probably ok, you'll get away with it"
  answer as correct.</p>
</blockquote>

<p>The available evidence (sparse!) suggests that it cannot be done (or can be in a restricted way, see technobabble below). A non-authoritative report (from a developer who had to drop it) is <a href="https://community.embarcadero.com/blogs/entry/ribbon-controls-in-rad-studio-10-1-berlin" rel="nofollow noreferrer">here</a>. A <a href="http://archive.is/YrReE" rel="nofollow noreferrer">snapshot of a MS support page</a> from 2013 on Office UI licensing for developers (also preserved on the <a href="https://web.archive.org/web/20130514015336/http://msdn.microsoft.com/en-us/office/aa973809.aspx" rel="nofollow noreferrer">Wayback Machine</a>) says:</p>

<blockquote>
  <p>The Office UI licensing program, originally launched in November 2006,
  has been retired. When the program was introduced in 2006, developer
  frameworks for the Office Ribbon did not exist. Microsoft tools and
  technologies now provide developers a variety of options, code, and
  developer frameworks for implementing the Office Ribbon UI in Windows
  applications.</p>
  
  <p>If you are a developer that already signed up for the Office UI
  licensing program and accepted the licensing terms, then you will
  continue to have rights under that license to implement the Office UI
  per the terms of that license. There are no changes at all for
  existing Office UI program licensees.</p>
  
  <p>If you are not already licensed to use the Office UI under the retired
  program, you can use any of the Microsoft tools and frameworks to
  implement the Ribbon UI in your current or future Windows
  applications. The license terms associated with the Microsoft
  developer framework will apply. For example, current developer
  frameworks that are licensed for creating a Ribbon UI include:</p>
  
  <p>Microsoft Ribbon for Windows Presentation Foundation (WPF)
  Windows Ribbon Framework
  Microsoft Windows SDK for Windows 7 and the .NET Framework 4
  Ribbon Extensibility Overview
  Microsoft Foundation Class Ribbon Component (The MFC ribbon may now be used under the same license as the Microsoft Windows SDK).</p>
  
  <p>If you are not already licensed under the Office UI licensing program,
  and you do not want to use any of the Microsoft tools and
  technologies, Microsoft no longer has a separate Office Ribbon UI
  licensing program. If you have any questions about the retired
  licensing program, please email the officeui@microsoft.com email
  alias.</p>
</blockquote>

<p>So apparently you can do it using MS tools, but not totally on your own.</p>

intellectual-property licensing