Microsoft overhauls security for publishing Edge extensions

Microsoft announced an updated Edge Publish API to strengthen the security of browser extension publishing, introducing dynamically generated per-developer API keys stored as hashes, internally generated access token URLs, and a 72-day key rotation policy. The opt-in change aims to reduce risks from credential theft and supply-chain attacks targeting extension developers, and requires developers to regenerate ClientId/secrets and update CI/CD pipelines, with a potential move to mandatory adoption in the future.