Update Visual Studio subscriber page with instant sandbox and commerce notes - #271
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: a8fee37c-5d86-4b10-9c48-cb9a5a4eed71
|
Learn Build status updates of commit 6741278: 💡 Validation status: suggestions
docs/join-with-visual-studio.md
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. |
PoliCheck Scan ReportThe 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 foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
There was a problem hiding this comment.
Pull request overview
Clarifies the Visual Studio subscriber onboarding experience by stating that Visual Studio subscribers use the same instant sandbox setup flow and (when applicable) the same commerce/add-on purchasing capabilities as other Microsoft 365 Developer Program members, with renewal behavior being the key difference due to Visual Studio linking.
Changes:
- Adds a new note explaining parity with instant sandbox setup and add-on purchasing capabilities for Visual Studio subscribers.
- Reiterates that renewal behavior is the only behavioral difference between joining directly vs via Visual Studio.
- Minor formatting/whitespace adjustments in the Visual Studio subscriber join instructions.
Suppressed comments (1)
docs/join-with-visual-studio.md:44
- This sentence implies add-on purchase capability is always present in both join paths. Since commerce capability can be conditional, it would be clearer to qualify this (or defer to the setup/FAQ guidance) so readers don’t assume add-on purchases are universally available.
In both cases, sandbox setup, sample data, and add-on purchase capability are the same — see [Set up a Microsoft 365 developer sandbox subscription](microsoft-365-developer-program-get-started.md). Renewal behavior is the only difference.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| > Your Microsoft 365 E5 developer subscription is for development purposes only and can be revoked if you use it for purposes other than development. For details, see the [Microsoft 365 Developer Program Terms and Conditions](terms-and-conditions.md). | ||
|
|
||
| > [!NOTE] | ||
| > Visual Studio subscribers go through the same instant sandbox setup as any other qualifying Developer Program member — see [Set up a Microsoft 365 developer sandbox subscription](microsoft-365-developer-program-get-started.md). The only difference is that you can link your subscription to Visual Studio for automatic renewal, as described below. Your sandbox includes the same add-on purchase capability (for example, purchasing Microsoft 365 Copilot licenses) as any other commercially enabled sandbox. |
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: a8fee37c-5d86-4b10-9c48-cb9a5a4eed71
|
Learn Build status updates of commit 85366a1: 💡 Validation status: suggestions
docs/join-with-visual-studio.md
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. |
PoliCheck Scan ReportThe 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 foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.
Suppressed comments (1)
docs/join-with-visual-studio.md:15
- The phrase "qualifying Developer Program member" is ambiguous in this doc (it could be read as a different Microsoft developer program). Using the full program name here improves clarity and consistency with the rest of the page.
> Visual Studio subscribers go through the same instant sandbox setup as any other qualifying Developer Program member. See [Set up a Microsoft 365 developer sandbox subscription](microsoft-365-developer-program-get-started.md).
Updates the Visual Studio subscriber page to clarify that VS subscribers go through the same instant sandbox setup as other members, with the same add-on purchase capability (including Microsoft 365 Copilot licenses). The only difference is automatic renewal via Visual Studio linking.