mc
M365 Message Center Archive
M365 Message Center Archive mirrors Microsoft 365 change posts
A static archive that refreshes Microsoft 365 Message Center and Roadmap data hourly for search.
What the archive does
The M365 Message Center Archive is a simple archive of the Microsoft 365 Message Center and the Microsoft 365 Roadmap. The readme states that Message Center and Roadmap data is refreshed hourly and the site is rebuilt every four hours, giving a searchable and viewable record of posts. The author built the site so it could be linked from a weekly newsletter called Entra.News, letting readers see a message center post without logging into the admin center. A caution box is clear that the site is for reference only and that users should always rely on their own tenant's Microsoft 365 message center post for the most accurate information, because not all posts are visible to all tenants and the archive is built from a small number of source tenants such as a Microsoft 365 E5 tenant. The readme also points out that a tenant may have different features and updates than what the archive shows. The project reports 33 stars and 8 forks on GitHub. The archive is hosted at mc.merill.net, and the readme emphasizes that posts are tenant specific, which shapes how the data should be read and cited. The rebuild every four hours keeps the search index current without a live database backend.
Agent skill and Discord notifications
The repository includes a skills.sh compatible agent skill for searching and citing the archive. The readme shows the install command npx skills add merill/mc, and explains the skill teaches agents to use the llms.txt file at mc.merill.net, search the messages-index.json file, cite canonical message pages, and remind users that Message Center posts are tenant specific. A Discord notification workflow runs on the hourly data refresh. It detects newly observed Message Center posts when either a service or product label or the title contains the standalone word Entra, case insensitively, then publishes one rich Discord embed per new post linking to the canonical archive page. Setup needs an incoming webhook named Entra Scout in the target channel, with its URL saved as the repository Actions secret DISCORD_ENTRA_SCOUT_WEBHOOKURL, reusing the same webhook and secret name in a companion EntraDiff repository so the two publishers share one Discord identity while keeping distinct message layouts and source labels. Posts are only announced when Microsoft published them within the last 14 days, controlled by the NewPostMaxAgeDays parameter on Update-Site.ps1, so adding a new source tenant does not flood the channel with old backlog. Delivery IDs and pending retries are persisted in a state file so reruns do not repost an existing post.
Tenants and configuration
Because Message Center posts are tenant specific, the archive collects them from every tenant listed in a build config file and merges the results. Each tenant contributes posts the others cannot see, and when the same message ID appears from more than one tenant, the copy with the newest LastModifiedDateTime wins, with a tie broken by the copy with the most body content. The readme documents the fields each tenant entry supports: a name used in the workflow log, a tenantId and clientId given as literal values or as environment variable placeholders, an auth method of clientSecret by default or federatedIdentity, a secretEnv for the client secret, an audience for federated credentials that defaults to api://AzureADTokenExchange, and a required flag that fails the run when true or logs a warning and continues when false, with the first tenant defaulting to required. A tenant whose IDs or secret are missing is skipped with a warning rather than failing the run, so the refresh keeps working before a new tenant is fully wired up. Adding a federated identity tenant is described as using workload identity federation. The project is published under the MIT license and is a practical reference tool for Microsoft 365 administrators who want a searchable, linkable history of change notifications without signing into the admin center each time.
Editorial conclusion
The repository is published under the MIT license and its most recent commit was on 2026-08-26.
Community notes