Open Bug 2041510 Opened 10 days ago Updated 3 days ago

Built in VPN Territory expansion

Categories

(support.mozilla.org :: Knowledge Base Content, task)

Product:
support.mozilla.org
Component:
Knowledge Base Content
Type:
task

Tracking

(Not tracked)

Status:
ASSIGNED

People

(Reporter: jcuevas, Assigned: ffloare)

Details

Did you check out the steps and FAQs for submitting requests to the CX content team? (yes or no)? [REQUIRED]

**Note: Learn more at https://mozilla-hub.atlassian.net/wiki/spaces/MSS/pages/21430745/Mozilla+Support+Content **

IMPORTANT NOTICE: FOR TIMELY PUBLICATION, CONTENT REQUESTS MUST BE SUBMITTED AT LEAST 14 DAYS BEFORE THE RELEASE DATE, ENABLING THE SUMO TEAM TO MAKE THEM LIVE WITHIN 48 HOURS POST-RELEASE. PLEASE ENSURE THAT ALL SUBMITTED INFORMATION, INCLUDING FEATURE DETAILS AND VISUAL ASSETS, IS FINAL. IN THE EVENT OF ANY UNFORESEEN CHANGES OR DELAYS NECESSITATING A PUSH TO A SUBSEQUENT RELEASE, PROMPTLY INFORM US TO PREVENT PUBLISHING AS PER THE ORIGINAL SCHEDULE.

Content access restriction: Is the content restricted to staff or under embargo (yes or no)? [REQUIRED]

Note: If yes, ensure ‘Advanced Fields’ are visible by selecting ‘Show Advanced Field’ at the top right, then scroll to ‘Security’ and check ‘Confidential Mozilla Employee Bug (non-security)’.

Attention: Any content not marked as confidential will be accessible to both NDAd and non-NDAd contributors with a Bugzilla account. Drafts for non-confidential content will also follow the same access policy, being open to comments for anyone with the link. Non-confidential Bugzillas can benefit from contributions by community contributors, while confidential Bugzillas will be handled exclusively by staff.

Product (ensure to select only one product for each ticket. If your request involves multiple products, file an individual Bugzilla for each)

Choose one below and delete others. [REQUIRED]
Firefox desktop

Select the type of request.

Choose one or more below and delete others. [REQUIRED]
KB content update/ new content

Please summarize the request, emphasizing any user-facing changes. Include historical context or background information if it helps users understand the new features or changes. [REQUIRED]

Firefox for Desktop is expanding VPN availability to the following locations as part of the wave 1 expansion:
Austria, Belgium, Bulgaria, Denmark, Finland, Ireland, Italy, Netherlands, Portugal, Spain, Sweden, Norway, South Africa, Malaysia, New Zealand, Singapore, Australia, Thailand, Chile, Colombia, Mexico. Japan will be a fast follow, but will NOT go live with the wave 1 expansion initially. As a result we need to update the note on KB article and add a new Common question to the foot of the article that lists all available locales.

  1. Update Progressive rollout note to refer to the common questions section for territory availability (ex. "Built-in VPN is only available in select locales. Check here(link to common question) for available regions."
  2. Add common question detailing available locations.

##Are the user-facing changes mentioned above for the production release, or is the feature/change experimental/ beta? (Production, Experimental or Beta) [REQUIRED]
**Note: Specify if the user-facing changes mentioned above are final, experimental, or in beta. This information is crucial for determining the appropriate support and documentation level needed. Please note that SUMO KB articles only support the production version for Firefox.
User facing changes is that the built-in VPN will be available in more non-english locales.

Are the new features or changes region-specific? Are they going to be released in a gradual rollout? [REQUIRED]

**Note: Please confirm if these features or changes are limited to specific geographic regions and if they will be implemented gradually. Knowing this helps us tailor our documentation and support resources appropriately.
Yes, region specific. Yes progressive rollout. See https://docs.google.com/document/d/1exGVpXIDRveFcyUAJjy0OI1lu2TgKN4uWmZMUGT-qTI/edit?tab=t.jy5tqlniw2c6 for more details

Please indicate if this is an on- or off-train release [REQUIRED]

**Note: If applicable, add the product version number to the end of the Summary field using the format: Summary [Product V123]. If this is an off-train release, please use the format: Summary [Product off-train].
Slightly off train. Release is June 2 - June 3rd 2026

What is the anticipated release date? [REQUIRED]

Note: Content is typically published at, or within, 48 hours of the release.
June 2nd-June 3rd

Does the content need to be published prior to the release date? If so, when? [REQUIRED]

Note: If you don’t let us know if this date changes, it will be published on this date
No

Does the content need to be localized in any languages outside of EN-US? If yes, please indicate which languages. [REQUIRED]

Note: A minimum of 10 days is required for translation requests.
Would be great to localize to supported languages for the named locales.

Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases. [REQUIRED]

Please include links to any design assets, visuals, figma files, etc. [REQUIRED]

Note: Ensure to submit only final visual assets relevant to the Production release, excluding Nightly or Beta images, and favor 'Light mode' UI screenshots over 'Dark mode'
https://docs.google.com/document/d/1exGVpXIDRveFcyUAJjy0OI1lu2TgKN4uWmZMUGT-qTI/edit?tab=t.jy5tqlniw2c6

Please add instructions for testing that will enable us to replicate the expected product behavior. [REQUIRED]

Does the content need approval before publishing? If yes, identify the one approver responsible for this task.

Note: Minor changes such as string updates are directly handled in SUMO, and will not lead to the generation of a pre-publishing draft. [REQUIRED]
Maysarah Buddin
Mark Toubman
Laura Lopez

Asana: https://app.asana.com/1/90589597529/project/1203460865189761/task/1215035087354072?focus=true

Assignee: nobody → ffloare
Status: NEW → ASSIGNED
Flags: needinfo?(jcuevas)

Shared with PM and other approvers

You need to log in before you can comment on or make changes to this bug.