nBold for Teams Is Now Microsoft 365 Certified

If part of your job is approving which Teams apps get installed in your tenant, you know the drill: a team wants a new app, and before it ships you need to know what it touches, what it stores, and whether it has actually been checked by someone other than the vendor. Most vendors hand you a security page and ask you to trust it. As of August 28, 2026, nBold for Teams doesn’t have to ask — Microsoft awarded it the Microsoft 365 Certification, valid for one year, with recertification required annually to keep it current.

What this certification means

The Microsoft 365 Certification is part of Microsoft’s App Compliance Program, which exists, in Microsoft’s words, “to increase customers’ trust in the applications used in their organizations.” The program runs in tiers. The entry tier, Publisher Attestation, is self-reported — a vendor fills out a questionnaire about its own practices. The Microsoft 365 Certification is the program’s highest tier: it requires an independent assessment of the app’s security and compliance controls, not a self-attestation.

Microsoft’s own description of what certified status represents: “Certified applications have been vetted against controls derived from leading industry frameworks and demonstrate the latest security and compliance practices to protect customer data.” The review doesn’t stop at the app itself — it also covers the practices and procedures of the publisher behind it, which is why the certification statement Microsoft requires alongside its logo is explicit that a publisher’s own practices still govern how data is handled, and that the certification is Microsoft’s validation that those practices are sound:

The Microsoft 365 Certification logo represents that this app has achieved Microsoft 365 Certification. In addition to app security, this program reviews the practices and procedures the app publisher employs. While customer data is under control of the app publisher, you can rest assured that Microsoft has validated that the app will handle it in a safe and secure manner.

How we got here

This certification lands at the end of a summer we spent specifically preparing for it. nBold commissioned an independent third-party penetration test of the application, and closed every finding it surfaced. Alongside that, we tightened security headers and cross-origin policy, hardened input handling across the app, and worked through a pass of dependency patching to keep the software supply chain current. None of that was cosmetic — it’s the same set of controls an independent assessor would go looking for, and it’s what made the certification assessment something we could go into with confidence rather than hope.

The Microsoft 365 Certification now sits alongside nBold’s existing ISO 27001 and SOC 2 Type II certifications, which cover the company’s broader information security management and operational controls. Where those two speak to how nBold runs as an organization, the Microsoft 365 Certification speaks specifically to the Teams app itself — a different, narrower, and independently assessed claim about the product you’re installing.

What it changes for you

Nothing changes in how nBold works day to day — there’s nothing to configure, no new setting to turn on, no workflow that shifts. What changes is what you can point to when you’re asked to justify the approval. The certification shows up in the compliance information Microsoft publishes for the app in the Teams admin center and the app store, alongside nBold’s listing in Microsoft AppSource. That means the status isn’t something you have to take our word for — it’s visible in the same place your security and procurement reviewers already check when they’re evaluating a Teams app.

If you’re the one who has to write the justification memo, that’s the practical difference: instead of describing nBold’s security posture from a vendor’s own security page, you can point to an independent, Microsoft-run certification with a defined recertification cycle. For IT admins managing app approvals at scale, that’s usually the difference between a review that takes a phone call and one that takes a meeting.

Related

See how nBold handles security, access, and governance in detail on the Security & compliance page, or book a demo to walk through it with your security team.