-
Notifications
You must be signed in to change notification settings - Fork 270
[Outlook] (event-based activation) Document requirements for Marketplace acquisition #5430
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 issues. Other issues are also a high priority. 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 |
|
Learn Build status updates of commit 00d5c27: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR documents the new unrestricted listing option for event-based Outlook add-ins in Microsoft Marketplace, allowing users to access event-based activation features without requiring admin deployment if certain requirements are met.
Key Changes:
- Introduces unrestricted listing option for event-based Outlook add-ins that meet Microsoft 365 Certification requirements
- Updates deployment guidance across documentation to reflect both restricted and unrestricted listing options
- Clarifies that admin deployment is only required for restricted listings, not all event-based add-ins
Reviewed Changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
| docs/publish/autolaunch-store-options.md | Adds comprehensive documentation on restricted vs unrestricted listing options, including comparison table, prerequisites, and unrestricted listing application process |
| docs/outlook/onmessagesend-onappointmentsend-events.md | Removes outdated statement requiring admin deployment for all Smart Alerts add-ins |
| docs/outlook/onmessagefromchanged-onappointmentfromchanged-events.md | Removes outdated statement requiring admin deployment for all event-based add-ins |
| docs/outlook/mobile-event-based.md | Removes outdated statement requiring admin deployment for all mobile event-based add-ins |
| docs/develop/event-based-activation.md | Expands deployment section with table showing deployment options by Office application and clarifies when admin deployment is required |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
|
Learn Build status updates of commit eaa2a6f: ✅ Validation status: passed
For more details, please refer to the build report. |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 issues. Other issues are also a high priority. 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 |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 issues. Other issues are also a high priority. 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 |
|
Learn Build status updates of commit 5d1194f: ✅ Validation status: passed
For more details, please refer to the build report. |
| | Listing features | Restricted | Unrestricted | | ||
| | --- | --- | --- | | ||
| | **Event-based activation support** | Add-in must be deployed by an organization's admin for the event-based activation feature to work. | Event-based activation works immediately upon installation by either the user or admin, without requiring admin deployment. | | ||
| | **Store searchability** | Users and admins can't explicitly search for the add-in in Microsoft Marketplace. They must use a specific flight code URL to install the add-in. | Users and administrators can explicitly search and install the add-in from Microsoft Marketplace. | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
depending on your answer to my previous comment about what's meant by explicitly in this context, I may have further suggestions for this entry
Co-authored-by: Elizabeth Samuel <elizs@microsoft.com>
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 |
|
Learn Build status updates of commit fe01604: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Learn Build status updates of commit 5978775: ✅ Validation status: passed
For more details, please refer to the build report. |
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 |
No description provided.