Validation policies for apps and add-ins submitted to Microsoft AppSource (version 2.2)
This document describes the criteria that are used to validate that Office Add-ins, SharePoint Add-ins, Microsoft Teams apps, and Power BI custom visuals are eligible to be listed in Microsoft AppSource. Solutions listed in Microsoft AppSource also appear in Office in the in-product Store.
1. Apps and add-ins provide value to the customer
|1.1||Your app or add-in must offer unique value or utility within the app or add-in experience that extends Office or SharePoint functionality for Microsoft AppSource customers.|
|1.2||Your app or add-in must work according to your description, and must not be in an unfinished state.|
|1.3||Your app or add-in's trial functionality must reasonably resemble its paid version.|
|1.4||Effective July 29th 2019, new add-ins accepted for publication to Microsoft AppSource must be free. Updates to existing paid add-ins will be supported until July 2020. For more information, see Moving from paid to free add-ins.|
2. Apps or add-ins can display certain ads
|2.1||Apps or add-ins can contain ads. The primary purpose of the app or add-in must be more than the display of the advertisement.|
|2.2||Ads in your app or add-in must comply with our content policies, described in policy 6.|
|2.3||Ads should not interfere with app or add-in functionality and should match our ad design guidelines.|
|2.4||The elements of your app or add-in's description, such as screenshots, text, and promotional images, must describe your app or add-in and not contain additional advertising.|
3. Apps and add-ins can sell additional features or content through purchases within the app or add-in
|3.1||Currently, Microsoft does not provide native application programming interfaces (APIs) to support purchases in apps and add-ins. You may use any third-party payment system for those purchases.|
|3.2||Where an app or add-in requires additional features to operate as advertised, to which an extra charge applies, you must clearly notify users in your description that those payments are required to access those features. Notification is also necessary if your app or add-in offers additional features or content for sale, either through purchases within the app or add-in or other means. If your free app or add-in contains an in-app purchase, the Microsoft AppSource listing for your add-in will reflect this by stating 'Additional purchase may be required' under the pricing options.|
|3.3||If your app or add-in collects credit card information or uses a third-party payment processor that collects credit card information, the payment processing must meet the current PCI Data Security Standard (PCI DSS).|
|3.4||Apps or add-ins running on iOS must not offer any additional features or content for sale.|
4. Apps and add-ins behave predictably
|4.1||Your app or add-in must not stop responding, end unexpectedly, or contain programming errors.|
|4.2||Your updated app or add-in must not decrease the app or add-in's functionality in a way that would be unexpected to a reasonable customer.|
|4.3||Your app or add-in description, imagery, documentation and any other associated metadata must be consistent with the functionality of the app or add-in.|
|4.4||You must provide instructions and links to resources in the submission form's testing notes that will be needed for Microsoft validation of your app or add-in. If, for example, your app or add-in requires a login/password, you must give Microsoft a pre-existing working login for testing purposes.|
|4.5||Your app or add-in must not make unexpected changes to a customer's document.|
|4.6||Your app or add-in must not jeopardize or compromise the security or functionality of Microsoft or third-party products.|
|4.7||The app or add-in must be free of viruses, malware, and any malicious software.|
|4.8||Your app or add-in must not launch functionality outside of the app or add-in experience without the explicit permission of the user.|
|4.9||No action should take more than three seconds to respond without some type of loading UX or warning.|
|4.10||Your app or add-in should not consume an unreasonable amount of memory that negatively impacts the performance of an average customer's environment.|
|4.11||Your app or add-in UI should not look unfinished.|
|4.12||Your app or add-in must be fully functional with the supported operating systems, browsers, and devices for Office 2013, Office 2016, SharePoint 2013, and Office 365. To download an Office 2013 trial, see Office 2013 - Microsoft Office 365 or Office 2013 - Microsoft Office 365 Business.
Your app or add-in's described features must work on a touch-only device without a physical keyboard or mouse.
|Word, Excel, and PowerPoint requirements:
|Add-ins must be fully functional with Windows 7, Windows 10, all versions of Internet Explorer 11 and later, and the latest versions of Microsoft Edge, Chrome, and Firefox.|
Web apps using Azure AD
|Web apps using Azure AD will no longer be accepted for submission to Microsoft AppSource. We recommend submitting Azure Web Apps via the Cloud Partner Portal.|
|4.13||Your SharePoint Add-in must not have remote debugging settings enabled.|
|4.14||The manifest for your SharePoint Add-in must not include the DebugInfo element.|
|4.15||Your SharePoint Add-in must not have any unauthenticated pages or APIs, with the exception of the error page.|
|4.16||The (unauthenticated) error page should not have links to other pages or other protected resources of the add-in.|
|4.18||Your add-in may not alter, or promote the alteration of, SharePoint or Office except via the Office and SharePoint Add-ins model.|
|4.19||Your app experience must not prompt a user to disclose the credentials of a Microsoft identity (for example, Office 365 or Microsoft Azure Organizational Account, Microsoft Account, or Windows Domain Account) except through Microsoft approved OAuth flow, where your app is authorized to act on behalf of the user.
For more information, see Context Token OAuth flow for SharePoint Add-ins and Authorization Code OAuth flow for SharePoint Add-ins.
|4.20||If your app or add-in depends on additional services or accounts, this dependency must be clearly called out in the description you submit.|
|4.21||Your app or add-in must not install or launch other executable code on the user's environment.|
5. Apps and add-ins put the customer in control
|5.1||You must submit a privacy link. The linked privacy documentation must be clearly titled as such and must clearly relate to your app, add-in, or overall service. Linked documentation that refers solely to your website is not acceptable. The content of the privacy statement must be under the direct control of the app or add-in provider and must contain, at a minimum, what user data is collected and stored, what privacy controls are protecting the users data, and how the data is used. If your app or add-in does not collect or transmit user information, you must link to a statement that states this fact.|
|5.2||Your app or add-in must obtain consent to publish personal information.|
|5.3||Your app or add-in must not obtain or store customer information or content without notifying the user.|
|5.4||Your app or add-in must not pass or transmit customer data without notifying the user.|
|5.5||Your app or add-in must protect customers from unintentional large data transfers over metered networks.|
|5.6||Your app or add-in must not implement geo-blocking of customers without explicitly stating this in the description.|
|5.7||Apps and add-ins must be secured with a valid and trusted SSL certificate (HTTPS). For more information, see Why do my apps and add-ins have to be SSL-secured? in the submission FAQ.|
|5.8||Apps and add-ins may not open pop-up windows unless they are triggered by explicit user interaction. Any pop-up windows that are triggered by user interaction must not be blocked by the browser's pop-up blocker when the pop-up blocker is set to the default value.|
|5.9||Your app or add-in cannot request unreasonably high permissions or full-control permission.
SharePoint Add-ins that request full-control permissions are not accepted in Microsoft AppSource.
If your app or add-in requires full-control permission, your Store add-ins might be dependent on add-ins that are deployed to a customer's tenant outside the Microsoft AppSource process. For more information, see Combining Microsoft AppSource add-ins with high trust permissions now supported.
|5.9.1||SharePoint Add-ins must prompt the administrator to explain that the add-in must install a full-control app. The administrator must be able to install this full-control app without interacting with the SharePoint Add-in provider, for example via email or web forms.|
|5.9.2||The full-control app that is installed via the SharePoint Add-in must comply with all Store policies.|
|5.9.3||If the full-control app meets the Microsoft AppSource validation policies, the SharePoint Add-in submitted to Microsoft AppSource can function only to install the full-control app.|
|5.10||You must specify an icon for your app or add-in in your add-in package or manifest, and that the icon must be correctly sized and formatted. For more information, see How can I avoid errors when submitting my app or add-in to Microsoft AppSource? in the submission FAQ.|
6. Apps and add-ins are appropriate for a global audience
|6.1||Your app or add-in must not contain adult content.|
|6.2||Your app or add-in must not contain content that advocates discrimination, hatred, or violence based on membership in a particular racial, ethnic, national, linguistic, religious, or other social group, or based on a person's gender, age, or sexual orientation.|
|6.3||Your app or add-in must not contain content or functionality that encourages, facilitates or glamorizes illegal activity.|
|6.4||Your app or add-in must not contain or display content that a reasonable person would consider to be obscene.|
|6.5||Your app or add-in must not contain content that is defamatory, libelous or slanderous, or threatening.|
|6.6||Your app or add-in must not contain content that encourages, facilitates or glamorizes excessive or irresponsible use of alcohol or tobacco products, drugs or weapons.|
|6.7||Your app or add-in must not contain content that encourages, facilitates or glamorizes extreme or gratuitous violence, human rights violations, or the creation or use of weapons against a person or animal.|
|6.8||Your app or add-in must not contain excessive or gratuitous profanity.|
|6.9||It is your responsibility to determine if you have the right to use the chosen name, content, logos, copyright, trademarks, code, online services and APIs.|
|6.10||Your app or add-in must not encourage, promote, or enable piracy of copyrighted content.|
|6.11||You must provide details on the submission form if your app or add-in calls, supports, contains, or uses cryptography.|
|6.12||Your app or add-in must not be designed or marketed to perform, instruct, or encourage tasks that could cause physical or psychological harm to a customer or any other person.|
|6.13||Effective August 2018, games are no longer accepted for publication to Microsoft AppSource.|
|6.14||Your app or add-in must comply with all applicable laws in the regions in which it is available.|
7. Apps and add-ins are easily identified and understood
|7.1||The metadata that you submit with your app or add-in must be accurate. For information about common mistakes to avoid, see How can I avoid errors when submitting my app or add-in to Microsoft AppSource? in the submission FAQ.|
|7.2||Your app or add-in must have a unique name.|
|7.3||Your app or add-in's title, description, and images must reflect its functionality, and may not mislead the user. If you make changes to your app or add-in such that the functionality does not match the description, you must resubmit your app or add-in.|
|7.3.1||The images submitted with your app or add-in must reflect its functionality, and must not mislead the user. They should be legible and clearly show the value proposition of the app or add-in. For more information about best practices for images, see Craft effective images.|
|7.4||Your app or add-in title and short description must convey its purpose. Do not rely exclusively on familiarity with a brand or service to convey the purpose of your app or add-in.|
|7.4.1||You must localize your app or add-in metadata (descriptions, screenshots, title) to be easily understood for each submitted languages.|
|7.4.2||The primary language selected when you submit your add-in must be one of the supported languages within your add-in's functionality as declared in your add-in's manifest.|
|7.4.3||This policy does not apply to dictionary add-in submissions.|
|7.4.4||You must specify language support for your add-in in your add-in's manifest.|
|7.4.5||If your app or add-in targets a larger organization or enterprise, the title can use your brand or service. For more information, see validation policy changes to support apps and add-ins that target larger organizations and enterprises. Microsoft Teams apps are not eligible to apply for this criteria.|
|7.4.6||Your short and long description must not be the same. Additionally, your short description must not be repeated within the long description.|
|7.5||Apps or add-ins listed in multiple languages must be easily identified and understood. Microsoft AppSource supports merchandising of apps and add-ins in the following languages:
Note: English apps and add-ins are distributed to all Store-supported markets by default. Providers can block English add-ins from distribution. For more information, see How do I declare language support for my add-in? in the submission FAQ.
|7.6||Your app or add-in must not falsely declare language support.|
|7.7||The capabilities you declare must relate to the core functions and description of your app or add-in.|
|7.8||You must provide at least one screenshot of your app or add-in.|
|7.9||Your add-in's packages must be correctly formatted and conform to the current manifest schema. For Office Add-ins, this is manifest schema version 1.1.
For detailed manifest schema information, see Schema reference for Office Add-ins manifests (v1.1) and Schema reference for manifests of SharePoint Add-ins. See also What are some common errors to avoid when submitting my add-in to Microsoft AppSource? in the submission FAQ.
|7.10||The categories you assign your app or add-in must correspond to the character or purpose of the app or add-in.
Note: Non-productivity apps or add-ins must be categorized in the Lifestyle category and only in that category.
|7.11||Your app or add-in must not be a duplicate of an app or add-in you've already submitted.|
|7.12||Your app or add-in must include the app or add-in name, version information, and technical support contact information that is easily discoverable.|
|7.13||The experience provided by an app or add-in must be reasonably similar in each language as declared in your add-in's manifest.
For more information, see How do I declare language support for my add-in? in the submission FAQ.
|7.14||Your add-in name may not include "app" or "plug-in" or derivatives.|
|7.16||You must specify a valid Support URL in the SupportURL element of your Office Add-in manifest.|
|7.17||If you wish to submit multiple variations of an app or add-in (for example, where different functionalities are unlocked at different price points), you must submit these separately, with separate product IDs.|
|7.17.1||Each app or add-in must have a unique name (for example, Test Add-in, Test Add-in: Premium).|
|7.17.2||The binary can remain the same across the multiple app or add-in listings.|
|7.17.3||We recommend, as a best practice, that you notify users that multiple app or add-in listings exist in the description for each. This ensures that users are aware that different cost/functionality tiers are available.|
|7.19||You may not use Microsoft product names in your app or add-in title.
Note: We may make some exceptions in cases where an add-in runs in multiple Microsoft products; for example, Contoso for SharePoint, Contoso for Outlook, Contoso for Office 365.
8. Updates to paid apps or add-ins must not decrease the app or add-in's functionality
|8.1||If you update your app or add-in's pricing/licensing terms, you must continue to offer the original functionality to the existing customer base at the original pricing. New prices and/or licensing terms may only apply to new users.|
|8.2||If you update your app or add-in's pricing from free to paid, existing users must receive the same level of functionality as before the update.|
|8.3||If you update your app or add-in from supporting site licenses for free to not supporting them, existing users must continue to be supported for free.|
|8.4||Your app or add-in cannot be resubmitted more than ten times per month, up to a total of 30 times per year.|
|8.5||If you withdraw your app or add-in from sale, you must ensure any external web services and/or web pages that support the app or add-in will continue to function for 90 days. Failure to do so will make you responsible for refund liability towards your customers.|
|8.6||Apps and add-ins may convert from free to subscription pricing. If you update your app or add-in's pricing from free to subscription, existing users must receive the same level of functionality as before the update.
Converting from a paid to a subscription app or add-in is not currently supported.
|9.1||If your app or add-in is found to violate any of our store policies, it can be removed from Microsoft AppSource. If a customer needs to be refunded, the refund will be deducted from any pending payouts to your account.|
10. Apps and add-ins utilize supported capabilities
|10.1||Your paid app or add-in must follow the Microsoft AppSource commerce requirements. For more information, see Can I submit a paid app or add-in to Microsoft AppSource? in the submission FAQ.|
|10.2||If your SharePoint Add-in has autohosting capabilities, it will not be accepted in Microsoft AppSource. For more information, see Update on Autohosted Add-ins Preview program.|
|10.3||The version number you specify for your add-in must exactly match the version number in the add-in manifest.
You must specify your add-in version using the following syntax:
a . b . c . d
Where a is an integer between 1-9999, and each of b , c , d are each integers between 0-9999. For example, 22.214.171.124 or 126.96.36.199.
Important When you resubmit add-ins with an updated manifest that includes a new version number, you must also make sure to update the version number in the submission form to match the version number of the new manifest.
|10.4||Add-ins that utilize deprecated functionality will not be allowed in Microsoft AppSource. For more information, see SharePoint 2013: List of obsolete types and members.|
|10.5||Paid Outlook add-ins must support a site license.|
|10.6||Submitting Office Add-ins that are hosted within Access as paid add-ins is not currently supported.|
For add-ins for iOS, you must also:
Accept Apple's Terms and Conditions by selecting the appropriate checkbox. Your Office Add-in must be compliant with all relevant Apple App Store policies.
Provide a valid Apple ID.
|10.8.1||For your Outlook add-in to be available on iOS or Android, it must comply with the Outlook add-in design guidelines.|
|10.8.2||The version of your add-in that runs on Office for iOS or Office for Android must not show any UI or language, or link to any other apps, add-ins, or websites, that ask the user to pay. Use of the term “free”, as in “free account”, is also not allowed. If the add-in requires an account, only free accounts can be created in the mobile version of the add-in. You can determine the length of time that the free account remains active (indefinitely or for a limited amount of time); however, if the user’s account expires, you cannot show any UI, text, or links to the user to indicate that they need to pay.|
|10.9||Office Add-ins must use version 1.1 of the Office.js library and the manifest schema.|
11. Add-ins provide a seamless and fluid experience for Microsoft AppSource customers
|11.1||Add-ins can fail validation for issues related to Office Add-in design guidelines and SharePoint Add-in design guidelines and which impede the customer experience within Office and SharePoint.|
|11.2||Add-ins that depend on external accounts or services must provide a clear and simple sign in/sign out and sign-up experience.|
|11.2.1||If your app or add-in targets a larger organization or enterprise and depends on external accounts or services, it must provide a clear and simple sign in/sign out experience. A sign-up experience is not required, as sign up will be managed by the enterprise outside of the app/add-in and not by the individual user.
For more information, see validation policy changes to support apps and add-ins that target larger organizations and enterprises.
|11.3||Your Office Add-in must provide a seamless first run experience, with a clear value proposition. If users must sign in or sign up, the value proposition must be clear to the user before they do so.|
|11.3.1||If your app or add-in targets a larger organization or enterprise, a seamless first run experience and value proposition is not required. However, your add-in must include either an email contact or a link in the UI that users can click to learn more about your services.
For more information, see validation policy changes to support apps and add-ins that target larger organizations and enterprises.
|11.4||The UI (buttons, links, text fields) of your add-in must be intuitive and obvious in their purpose. Users must not be required to read support content to perform basic operations. For more information, see Best practices for developing Office Add-ins.|
12. Office Mix Add-ins
|12.1||Office Mix Add-ins must be for an educational purpose.|
|12.2||Office Mix Add-ins must be created using the Office Mix platform.|
|12.3||Office Mix Add-ins must be free.|
|12.4||Office Mix Add-ins must start in the Play View when published to Office Mix.|
|12.5||All restrictions that apply to content add-ins for PowerPoint also apply to Office Mix Add-ins.|
13. Power BI custom visuals
|13.1||Power BI custom visuals must be free. Power BI custom visuals can offer additional purchases. If your Power BI custom visual offers an additional purchase, it must comply with the IAP guidelines. For details, see Guidelines for Power BI visuals with additional purchases.|
|13.2||Power BI custom visuals submitted to Microsoft AppSource must be accompanied by a sample file included in the same location as the pbviz file, with the .pbix format. For the best user experience, consider adding Hints and Tips for using the Visual to the sample file.|
|13.3||Your custom visual must support Power BI Desktop, Power BI Online, Power BI mobile apps, and Power BI Windows universal apps. It must be compatible with Windows 10 and the latest versions of Microsoft Edge, Chrome, Firefox, and Safari (Mac OS).|
|13.4||Your custom visual must support the core functions of Power BI for that visual type, including, but not limited to:
Pinning to dashboard
Various data types
14. Microsoft Teams apps
|14.1||Your Microsoft Teams app must be free.|
|14.3||Your Microsoft Teams app must not launch functionality outside of the Microsoft Teams app experience without the explicit permission of the user.|
|14.5||Microsoft Teams apps must respond in a reasonable time frame.|
|14.5.1||For tabs, if a response to an action takes more than three seconds, you must provide a loading message or warning.|
|14.5.2||For bots, a response to a user command must occur within two seconds. If longer processing is required, you must use a typing indicator.|
|14.5.3||For compose extensions, a response to a user command must occur within five seconds.|
|14.6||Your Microsoft Teams app must be fully functional on the following operating systems and browsers:
Window 7 and later
Mac 10.10 and later
Microsoft Edge 12 and later
Firefox 47.0 and later
Chrome 51.0 and later
Your bot experience must be fully function on iOS (9.0 and later), Android (4.4 and later), and Windows Phone (10.0.10586 and later).
|14.7||You must submit a Terms of Service link.|
|14.8||For bots and compose extensions, you will need to ensure that you follow the privacy notice requirements as communicated in the Developer Code of Conduct for the Microsoft Bot Framework.|
|14.9||Your bot and compose extension must operate in accordance with the requirements set forth in the Microsoft Bot Framework Online Services Agreement and Developer Code of Conduct for the Microsoft Bot Framework.|
|14.10||Your Microsoft Team app’s package must be correctly formatted and conform to the latest manifest schema. This is currently manifest schema version 1.5.|
|14.11||For bots, all manifest information must be consistent with your bot’s Bot Framework metadata: bot name, logo, privacy link, and terms of service link.|
|14.12||Your Microsoft Teams app name may not include "app", "plug-in", or derivatives.|
|14.13||The UI (buttons, links, text fields) of your Microsoft Teams app must be intuitive and obvious in their purpose. Users must not be required to read support content to perform basic operations.|
|14.14||Microsoft's review and publication of your Microsoft Teams app to the Microsoft Teams gallery is not an endorsement of your Microsoft Teams app.|
|14.15||Microsoft Teams apps can fail validation for issues related to Microsoft Teams app design guidelines or issues that impede the customer experience within Microsoft Teams. To pass validation, Microsoft Teams apps must meet requirements 14.15.1 through 14.15.9.|
|14.15.1||A tab experience must provide value beyond simply hosting an existing website: A tab must fulfill a valid user scenario within it|
|14.15.2||Content in a channel tab must be contextually the same for all members of the channel and not scoped for individual use.|
|14.15.3||Content in a tab should not have excessive chrome or layered navigation (also known as "chrome").|
|14.15.4||A configurable tab should not allow users to navigate outside the core experience within the same tab.|
|14.15.5||The configuration screen of a configurable tab must clearly explain the value of the experience and how to configure it.|
|14.15.6||Tab configuration must happen in the configuration screen.|
|14.15.7||Bots must be responsive and fail gracefully with a way forward. Bots must respond to any commands entered by the user and must not dead-end the user.|
|14.15.8||Your bot must include a help command that provides your value proposition along with all your valid commands.|
|14.15.9||Bots must send a welcome message on first launch.|
|14.16||Microsoft Teams apps must focus on the Microsoft Teams experience and should not include names, icons, or imagery of other similar chat-based collaboration platforms or services unless the apps provide specific interoperability.|
|14.17||Apps that depend on external accounts or services must provide a clear and simple sign-in/sign-out and sign-up experience. Microsoft Teams apps that depend on authentication to an external service to allow content sharing in channels must clearly state in their help documentation (or similar location) how a user can disconnect or unshare any shared content (if the same feature is supported on the external service). The ability to unshare this content does not have to be present in the Microsoft Teams app, but the process should be clearly documented, and the documentation should be accessible from within the app.|
|14.18||To help to ensure the security of your app and users, domains outside of your organization's control (including wildcards) and tunneling services cannot be included in the valid domains in your manifest. Exception: If you're using OAuthcard,
|14.19||Teams apps must provide a suitable path for users to sign up for access.|
|14.20||Teams apps must use persistent/silent authentication in a capability. We recommend using persistent authentication, see Silent authentication.|
|14.21||The policies outlined in Section 2 do not apply to Microsoft Teams apps. Microsoft Teams apps may not display ads.|
15. Add-ins with Excel custom functions
|15.1||Add-ins that contain custom functions must support add-in commands. This is to ensure that users can easily discover your add-in.|
|15.2||Your custom functions metadata must have the helpUrl property set. For an example, see Custom functions metdata.|
|15.4||Your add-in must work across all platforms that support custom functions. Your add-in must also define in the Requirements element the following requirement set
|15.5||After an add-in is approved using the EquivalentAddins tag in the manifest, all future updates to the add-in must include this tag. This tag ensures that your custom functions save in XLL-compatible mode.|
|15.6||To help ensure an efficient validation process, if your add-in contains custom functions, you must provide test notes to validate them on submission.|
As these requirements evolve, we will continue to update our documentation. Stable requirements are critical to your doing your best work, so we aim to ensure that the changes we do make are sustainable and continue to protect and enhance your add-ins.
Thank you again for joining us in this commitment to delivering fantastic experiences.
Validation policy change list
|2.2||December 16, 2019||Updated policy 14.15.|
|2.2||December 6, 2019||Added policies 14.19, 14.20, and 14.21.|
|2.2||December 4, 2019||Update policy 14.15.|
|2.2||September 23, 2019||Updated policy 14.18.|
|2.2||August 24, 2019||Updated policy 14.18.|
|2.2||July 12, 2019||Added policy 1.4.|
|2.2||June 6, 2019||Updated policy 14.10.|
|2.2||May 6, 2019||Added section 15.|
|2.2||April 19, 2019||Updated policy 14.10.|
|2.2||April 04, 2019||Added policy 14.19.|
|2.2||December 03,2018||Updated policy 13.1.|
|2.2||November 19,2018||Updated policy 7.4.5.|
|2.2||December 03, 2018||Updated policy 13.1.|
|2.2||November 19, 2018||Updated policy 7.4.5.|
|2.2||September 11, 2018||Updated policy 4.12.3.|
|2.2||August 20, 2018||Updated policy 6.13.|
|2.2||August 20, 2018||Removed policy 7.18.|
|2.2||July 4, 2018||Updated policy 3.2.|
|2.2||June 11, 2018||Added policy 7.4.6.|
|2.2||May 16, 2018||Updated policy 5.1.|
|2.2||March 30, 2018||Added policy 5.9.|
|2.2||March 8, 2018||Added policy 14.18.|
|2.2||February 20, 2018||Updated policies 13.3, 14.6, and 14.10.|
|2.2||February 19, 2018||Updated policy 7.3.1.|
|2.2||January 22, 2018||Updated policy 7.17.2.|
|2.2||January 11, 2018||Added policy 14.17.|
|2.2||January 4, 2018||Updated Office Store to Microsoft AppSource throughout page.|
|2.2||August 9, 2017||Updated policy 10.8 to apply to Office for Android, and added policy 10.8.2.|
|2.2||August 4, 2017||Added policies 14.15 and 14.16.|
|2.2||July 21, 2017||Added policy 7.19.|
|2.2||July 7, 2017||Removed policy 14.4. Updated policies 14.5, 14.6, 14.8, and 14.9.|
|2.2||May 4, 2017||Added section 14 for Microsoft Teams apps.|
|2.1||February 15, 2017||Updated policy 4.12.1 for Outlook add-ins.|
|2.1||February 8, 2017||Added section 13 for Power BI custom visuals.|
|2.0||January 23, 2017||Updated policies 4.12.2 and 4.12.3.|
|2.0||January 17, 2017||Clarified policy 5.8.|
|2.0||January 9, 2017||Updated policy 4.12.1 to state that add-in commands are required for Word, Excel, and PowerPoint add-ins that use the taskpane manifest, effective Feb 1, 2017.|
|2.0||November 30, 2016||Added new validation policies for apps and add-ins that target larger organizations or enterprises: 7.4.5, 11.2.1, 11.3.1|
|1.9||April 19, 2016||Updated policies 4.12, 5.9, and 7.3. Added policies 7.4, 11.3, 11.4.|