Hi everyone, We are going to be renaming the 'meek-azure' built-in bridge type to 'meek' in Tor Browser Alpha 15.0aX and and some of the surrounding ecosystem in the relatively near future. For background, see this issue: - https://gitlab.torproject.org/tpo/applications/team/-/issues/37 This will affect you *sooner* (i.e. in the coming month or two) if you: - consume pt_config.json: https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/blob/main... - If you populate your own application's built-in bridges from this file you may need to implement settings migration logic, in-app string updates, etc; in the future the 'meek-azure' key on the 'bridges' object will be just 'meek' - use the name 'meek-azure' or reference Azure in your app; the built-in 'meek-azure' bridges don't actually run on Azure anymore so if your app references Azure or Microsoft, you should probably update your copy - See this issue for updating Tor Browser's strings for reference: - https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/44069 This will affect you *later* (i.e. in the coming several months to a year) if you consume: - rdsys censorship circumvention APIs to query bridges by 'builtin' type - the high-level plan is to add meek-azure -> meek shims on the server-side so any legacy clients will still work into the future (though at some point such shims will surely be dropped) - new callers should instead request 'meek' bridges rather than 'meek-azure' - issue is being tracked here: https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/272 One thing to note is that this dose not affect the actual bridge-lines or pluggable-transport client configuration lines which are given to tor. The underlying pluggable-transport is still 'meek_lite', the rename only really affects the user-visible 'meek-azure' name. Please let me know if you've any questions/concerns! best, -morgan