What is outlook-k12?

This project is a lightweight web console for automating registration using pools of Outlook email accounts. A user pastes in a list of Outlook accounts, each formatted as email, password, client id, and refresh token, and the tool automatically handles the email verification code step of a signup flow using Microsoft's OAuth system. After registration, each account can be joined to a specified workspace by its workspace id, and the console then exports the resulting account credentials as JSON formatted for a separate tool called sub2api. The README lists several core features: support for either raw email addresses or plus-style email aliases, adjustable concurrency and retry settings for batch runs, automatic joining of a target workspace after registration with a refreshed workspace-scoped access token, and a browser based console for starting tasks, viewing logs, and downloading results. Task history, logs, and result summaries are saved to a local SQLite database so a page refresh does not lose configuration. After a successful upload to sub2api, the tool by default deletes local token files and clears sensitive fields from its database. Setup involves installing Python dependencies and running the console locally with uvicorn, or deploying it as a single Docker container with a mounted data volume, intended for use on a VPS. The README documents environment variables for the database path and batch run storage location, and recommends setting an API key header if the console is exposed publicly. It also includes a troubleshooting section covering proxy timeout issues, noting that VPS data-center IP addresses often trigger anti-abuse detection during registration, and recommending low concurrency values between one and three accounts at a time. The README includes explicit security advice: never commit environment files, database files, task output, logs, or token files to version control, never post real Outlook account lines in the README or an issue, and always set an API key when deploying the console publicly. It credits the LINUX DO community for support and discussion. The README does not explain what the target registration service is beyond referring to it generically, or provide further detail on how sub2api itself is used.