LoopAI-103
Read this lesson

Before release

With the harms mapped, a way to measure them, and mitigations in place, you're ready to prepare for release. Think of it like opening a new bridge: a few steps make the opening go well, and keep traffic flowing safely afterwards. First, finish your prerelease reviews, the inspectors' sign-off. Work out which compliance rules apply in your organization and your industry, and give the right teams time to review the system and its documentation. The usual reviews cover legal, privacy, security, and accessibility.

Release and operate

Then the release itself needs a plan. Roll it out in phases, first to a small group of users, so you can collect feedback and fix problems before a wider launch, like letting pedestrians cross before the cars. Write an incident response plan, with estimates of how quickly you can respond when something unexpected happens: the rescue boat on standby, stopwatch in hand. Write a rollback plan with the steps to put the solution back to an earlier version if an incident happens, like barriers that can switch the lanes back. Make sure you can block harmful responses the moment they're discovered, and block specific users, apps, or client IP addresses if someone misuses the system, like a tollbooth that can stop one particular vehicle. Give users an easy way to send feedback and report problems, especially to flag generated content as inaccurate, incomplete, harmful, offensive, or otherwise wrong. And collect telemetry to measure how satisfied users are, and to find features that are missing or hard to use, like counters on the bridge. Whatever telemetry you gather has to follow privacy laws, and your organization's own privacy policies and promises to users.

Facts from Microsoft's documentation: Overview of Responsible AI practices for Azure OpenAI in Foundry Models (CC BY 4.0), rewritten in Loop's own words and examples. Narration, animation, and quiz by Loop. Microsoft, Azure, and Microsoft Foundry are trademarks of Microsoft. Loop is independent and not affiliated with or endorsed by Microsoft.