RECO
    Back to blog
    Responsible AI

    How Microsoft Uses Responsible AI to Make AI Enterprise-Ready

    Markus C. Weiss, BScMarkus C. Weiss, BScCTO, RECOPublished Last edited 6 min read

    Microsoft's six Responsible AI principles now appear in plenty of slide decks: fairness, reliability and safety, privacy and security, inclusiveness, transparency, accountability. For a mid-sized company, I think they are the least useful part of what Microsoft has published on the subject. It gets useful one level down, in the Responsible AI Standard v2 from June 2022. That document says who has to check what, and when. The audit disaster adds an evidence preparation perspective on traceable review responsibilities. For SMEs, knowledge validation translates that mechanism into named review responsibilities, while knowledge transfer ensures colleagues understand checks and exceptions rather than merely receiving a principles poster. You can copy that mechanism. You don't need the poster with the principles.

    The usual objection is that responsible AI is for corporations with their own ethics department, and that a mid-sized company cannot afford it. I disagree, because the parts worth having fit on a single page. The expensive part comes later, when an AI recommendation in a personnel decision or a customer contract turns out to be wrong and nobody can say who approved it.

    What Microsoft actually does

    The principles are headlines. The Standard turns each of them into goals with concrete requirements. Under accountability, for example, you find an impact assessment (A1), oversight of significant adverse impacts (A2), fitness for purpose (A3), data governance and management (A4) and human oversight and control (A5). Under transparency, goal T3 requires that people are informed when they are interacting with an AI system.

    Two rules from the Standard transfer directly, in my view. The impact assessment happens early, typically when the product vision and requirements are defined, not just before rollout. And it is reviewed at least once a year, plus whenever a new intended use is added (A1.3). Under A5 the Standard explicitly names the risk of over-relying on system output, known as automation bias.

    According to Microsoft's 2025 Responsible AI Transparency Report, higher-risk uses and generative AI releases go through a pre-deployment review and red teaming, and the Standard's requirements are documented through an internal workflow tool. The summary does not say how many cases were reviewed. Keep that gap in mind as you read: it is a self-report.

    The six principles as questions for your business

    Instead of explaining the principles, I turn each one into a question you can answer for a specific use case.

    • Fairness: does the system rate or rank people, such as applications or performance data? If so, spot-check whether particular groups consistently come out worse.
    • Reliability and safety: what happens when the system fails or produces nonsense? You need a defined way back to the manual process.
    • Privacy and security: where is the data processed, how long is it kept, and does the vendor use it for training? An employee review is not training material.
    • Inclusiveness: does the system work for the colleague in the warehouse, for regional dialects and for people with poor eyesight? A tool that serves only one group well widens internal gaps.
    • Transparency: can the people affected see that AI was involved, and can a recommendation be traced back to its source?
    • Accountability: which named person answers for this use case? "IT" does not count.

    None of these needs an ethics board. Each needs one person who writes the answer down.

    From principle to operating model: Govern, Map, Measure, Manage

    For operations, Microsoft points to the AI Risk Management Framework 1.0 published by the US agency NIST in January 2023, and says its published case studies are grounded in it. The framework is voluntary and organises the work into four functions. Govern is not a phase; NIST describes it as cutting across everything else. Here is what that looks like in an SME.

    Take a typical use case, sketched freely rather than drawn from a real client. A consulting firm wants to make its internal project reports and meeting minutes searchable with AI. New hires should be able to look up for themselves what used to take a long string of corridor conversations.

    Govern: who decides

    Management names one person responsible for the system, in this example the head of knowledge management. It is written down who approves new data sources, who may switch the system off and when the review takes place, which the Microsoft Standard requires at least once a year. Without this layer you get shadow IT, with every team uploading its documents to a different tool.

    Map: understand the risks before launch

    Before launch the team settles three things. Which data goes in, and does it include personnel files or employee reviews? Who may see which answers, so that confidential client projects don't show up in another team's search results? And what is the worst realistic error, such as an outdated fee agreement presented as current? The team then deliberately tries to get the system to give exactly that kind of answer.

    Measure: make the impact measurable

    Measure a few things everyone understands: the share of answers with a verifiable source, the share that subject experts mark as wrong in a regular sample drawn from a fixed set of test questions, and how long it takes new staff to answer a typical project question on their own. Without these numbers, nobody knows at the next review whether the system delivers what the pilot promised.

    Manage: control in live operation

    In operation, people stay in charge. Users can flag answers as wrong, flagged errors go to the responsible person, and for sensitive content a human decides before anything is passed on. If the error rate in the sample rises, the source in question comes out of the index until it has been cleaned up.

    The effort is mostly alignment, and the result fits on one page. Much of it overlaps with what the EU AI Act expects from deployers anyway. Our article on the EU AI Act in practice sets out the specific obligations.

    How we translate the principles in RECO

    RECO makes conversations such as employee reviews, jour fixes and project handovers searchable. That puts us at the most sensitive end of almost every principle, because the content is people talking about people.

    • Privacy and security: processing runs on servers in the EU, on a dedicated server in Germany, and on-premises for companies with stricter requirements.
    • Transparency: every answer points to the conversation or document it came from. Whoever reads it can check the passage themselves.
    • Human oversight: the AI proposes summaries and agreements, and the manager approves them. Our article on human in the loop explains why we made that a founding principle.
    • Accountability: a person decides whether something said in a conversation feeds into feedback, a promotion or a handover. The model supplies context.

    A test for your next AI rollout

    Before you approve an AI system for a new purpose, four answers should be on one page: who is responsible, which data goes in and who sees it, how you will know at the first review whether it works, and when the next review is due. If one is missing, the system is not ready, however good the demo was. Microsoft's principles give you the headings. The work is in those four lines.

    Sources

    Related articles

    In a 30 minute software demo we show you how RECO secures and transfers knowledge in your company. Request a demo now and we'll get back to you with a proposed time.