Revise FAQ for Microsoft 365 Developer Program

[akagarwa-msft]

Updated the Microsoft 365 Developer Program FAQ with new information on eligibility, subscription details, and sandbox capabilities. Adjusted the ms.date to reflect the latest update.

[learn-build-service-prod]

Learn Build status updates of commit 0bdbc0f:

💡 Validation status: suggestions

File	Status	Preview URL	Details
docs/microsoft-365-developer-program-faq.yml	💡Suggestion	View	Details

docs/microsoft-365-developer-program-faq.yml

• Line 24, Column 13: [Suggestion: other-site-link-broken - See documentation] Link 'https://developer.microsoft.com/microsoft-365-copilot' points to a page that doesn't exist. Check the path or URL and update the link.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

[learn-build-service-prod]

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

[Copilot]

Pull request overview

Updates the Microsoft 365 Developer Program FAQ to reflect current eligibility paths, sandbox provisioning details, commerce/billing behavior, and lifecycle expectations, along with a metadata refresh date.

Changes:

• Reworked the opening/overview content and added an “instant sandbox” FAQ entry.
• Expanded eligibility, sign-in/account management, and subscription lifecycle guidance (including commerce-enabled sandbox behavior starting July 2026).
• Added a new “Billing and commerce” section and updated licensing/capabilities explanations.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[learn-build-service-prod]

Learn Build status updates of commit 0216913:

💡 Validation status: suggestions

File	Status	Preview URL	Details
docs/microsoft-365-developer-program-faq.yml	💡Suggestion	View	Details

docs/microsoft-365-developer-program-faq.yml

• Line 24, Column 13: [Suggestion: other-site-link-broken - See documentation] Link 'https://developer.microsoft.com/microsoft-365-copilot' points to a page that doesn't exist. Check the path or URL and update the link.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

[learn-build-service-prod]

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (6)

docs/microsoft-365-developer-program-faq.yml:294

• This answer ends with a cross-reference link but no terminal punctuation. Add a period after the closing parenthesis.

          If your sandbox has commerce capability enabled, yes — see [Purchase Copilot licenses from your M365 Developer Program sandbox](purchase-copilot-licenses.md) for steps. Not all Developer Program tenants currently support Copilot purchases; see [Do all Developer Program members get a commercially enabled sandbox?](#do-all-developer-program-members-get-a-commercially-enabled-sandbox-)

docs/microsoft-365-developer-program-faq.yml:30

• The instant sandbox description currently starts with an absolute claim ("Every qualifying developer subscription is provisioned as an instant sandbox"), but the docs set also describes configurable sandboxes. Reword this to define what an instant sandbox is without implying it’s the only sandbox type.

          Every qualifying developer subscription is provisioned as an instant sandbox, which is a fully pre-configured tenant that's ready to use within minutes. It comes pre-provisioned with Microsoft Teams, SharePoint, Outlook, and Office; 24 test users plus one admin; and pre-installed sample data (including Microsoft Graph user/mail/calendar data and a Teams sample data pack) that simulates an enterprise environment.

docs/microsoft-365-developer-program-faq.yml:124

• This answer conflicts with the earlier statement that Visual Studio Professional/Enterprise subscribers qualify for a developer subscription (which many Microsoft employees may also have). Consider clarifying that employees can’t request through the Developer Program and should use the Visual Studio benefits route instead, to avoid contradictory guidance within the same FAQ.

          As a full-time Microsoft employee, can I receive a subscription?
        answer: |
          No. Microsoft employees cannot request a sandbox through the Microsoft 365 Developer Program due to internal corporate policies.

docs/microsoft-365-developer-program-faq.yml:108

• This paragraph ends without terminal punctuation, which reads like an incomplete sentence in the rendered FAQ. Add a period after the closing link.

          For Premier or Unified Support customers, access to the program is handled through their Microsoft partner contact rather than the self-service dashboard button. See [Who qualifies for a Microsoft 365 E5 developer subscription?](#who-qualifies-for-a-microsoft-365-e5-developer-subscription-)

docs/microsoft-365-developer-program-faq.yml:276

• This answer states that 16 non-admin users are prepopulated for every sandbox at setup time, but elsewhere in the docs sample users are tied specifically to instant sandboxes (and configurable sandboxes can install packs later). Make the condition explicit to avoid misleading guidance.

          Your subscription includes 25 user accounts, including one administrator account. 16 of the 24 non-admin user accounts are prepopulated for you when your sandbox is set up. You can manage the users in your subscription via the admin center.

docs/microsoft-365-developer-program-faq.yml:286

• This answer ends with a cross-reference link but no terminal punctuation. Add a period after the closing parenthesis.

This issue also appears on line 294 of the same file.

          Support for add-on purchases depends on whether your sandbox has commerce capability enabled. Instant sandboxes provisioned starting July 2026 for new eligible enterprise customers support purchasing eligible add-ons, such as Microsoft 365 Copilot; sandboxes without commerce capability enabled don't support the same purchasing experiences. See [Do all Developer Program members get a commercially enabled sandbox?](#do-all-developer-program-members-get-a-commercially-enabled-sandbox-)