Verification of marketplace item

[samsmithnz]

A very large Azure DevOps customer I'm working with enquired today why this isn't published by Microsoft and verified. They are unable to use unverified 3rd party marketplace items.

https://marketplace.visualstudio.com/items?itemName=bewhite.ps-rule

Note that the GitHub Actions version is verified. https://github.com/marketplace/actions/psrule

Are there any plans to do verify this for Azure DevOps?

[BernieWhite]

@samsmithnz Thanks for your interest in PSRule and the question/ request.

Previously there were some internal restrictions about how this process occurs. The process for onboarding a verified GitHub Action was able to be done however the Visual Studio Marketplace has different requirements.

That was a little while ago now so it's worth re-investigating if these are still an issue to move forward with this request.

[BernieWhite]

@samsmithnz Circling back on this one. Great news, we are going to move forward with a Microsoft verified publisher.

This means that over the next few releases we will be preparing to move the extension to this new publisher. Unfortunately we can't switch the existing extension to a new verified publisher, so the experience will be as follows:

• Publish a new extension under the ps-rule publisher, verified as Microsoft.
• Both new extension and existing extension will be published for a period of time.
• The existing extension will be updated to generate a warning advising customers to start using the new extension. Customers will need to uninstall the old extension from their Azure DevOps organizations and install the new extension to continue receiving updates.
• All going well, updates to the previous extension will cease from PSRule v3.

---

Things to note:

• An organization owner (Project Collection Administrators) will be required to uninstall to previous extension then install the new extension from their Azure DevOps organization.
• Customers will not need to update their pipelines to use the new extension, the same names and IDs will be carried over.
• Customers will not be able to install both the new and old extension in the same Azure DevOps organization, however can install the new extension in a new/ separate organization for testing prior to switching to the new extension.

We feel this approach minimizes disruption and rework customers need to complete to adopt the new verified extension.

[samsmithnz]

Congratulations! Exciting news.

[olegd-superoffice]

So there's still no official Microsoft release?