Skip to content

Update spe-da.md #10208

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

Merged
merged 4 commits into from
May 5, 2025
Merged

Update spe-da.md #10208

merged 4 commits into from
May 5, 2025

Conversation

clalissayi24
Copy link
Contributor

Added details to Note section around PAYG feature and availability.

Category

  • Content fix
  • New article

Related issues

  • fixes #issuenumber
  • partially #issuenumber
  • mentioned in #issuenumber

What's in this Pull Request?

Update to the note section to include PAYG feature availability.

Submission guidelines

  • !!IMPORTANT!! - All submissions must complete the baseline sections included in this template. Ignoring or deleting this template may result in closing the issue with the label type:incomplete-submission.
  • Follow our guidance on How To Create Good Pull Requests.
  • Target the main branch of this repo.
  • When changing a page, ensure you update the ms.date front matter wih the current date in the format MM/DD/YYYY.
  • Review all build checks and address the automated errors, warnings, and suggestions.
  • NOTE: The live site is based on the live branch. Site owners periodically refresh live branch from the main branch so merged PRs won't immediately appear on the live site. Please be patient to see your changes appear on the live site.

Added details to Note section around PAYG feature and availability.
Copy link
Contributor

Learn Build status updates of commit 91e7ab8:

✅ Validation status: passed

File Status Preview URL Details
docs/embedded/development/declarative-agent/spe-da.md ✅Succeeded View

For more details, please refer to the build report.

For any questions, please:

@clalissayi24 clalissayi24 marked this pull request as draft April 29, 2025 17:22
@cindylay
Copy link
Contributor

just requested @tonchan-msft and myself for review. When its ready to go draft --> PR then you can request andrew

@@ -11,7 +11,9 @@ ms.localizationpriority: high
>
> SharePoint Embedded copilot is currently in private preview. Stay tuned for latest API and SDK changes on this page.
>
> Currently, to use SPE copilot, the consuming tenant user of the application is required to have a [Microsoft 365 Copilot license](/copilot/microsoft-365/microsoft-365-copilot-licensing). In the future, the license-based model will be replaced with a consumption-based model. Stay tuned for billing model announcements during the preview period.
> SPE copilot consumption-based model will soon be available this coming May! Starting May 1st, Standard billing model will be available to all private preview customers, and this roll out is expected to complete by May 15, 2025. This means that starting May 15th, to access SPE copilot within SPE applications, you will need to use standard container type and the copilot interactions, including those from Copilot license users, will be billed to the Azure subscription associated with your Container Type. Learn more about [SharePoint Embedded billing management](/sharepoint/dev/embedded/administration/billing/billingmanagement).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Considering we are still reviewing on 4/29, does the line "SPE copilot consumption-based model will soon be available this coming May! " make sense?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Starting May 1st," "complete by May 15, 2025". Lets have a standard convention for dates.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"you will need to use standard container type" "billed to the Azure subscription associated with your Container Type". Lets standardize "container type" vs "Container Type"

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"to access SPE copilot within SPE applications" - this potentially opens question on "how about accessing SPE copilot outside of SPE apps"? Do we need to frame this line this way?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated based on your feedback for comments 1-3.
For 4 - the messaging is intended more to be around to USE spe copilot in an spe app, rather than talking about the scope of how spe agents will reason over SPO/SPE data... am I understanding your concern accurately? What if I made the change to "to use SPE copilot within SPE applications" (getting rid of the word "access") - does that help?

@tonchan-msft tonchan-msft requested review from javieralvarezchiang and removed request for javieralvarezchiang April 29, 2025 19:51
Updated based on Tony's feedback
Copy link
Contributor

Learn Build status updates of commit 3dff02d:

✅ Validation status: passed

File Status Preview URL Details
docs/embedded/development/declarative-agent/spe-da.md ✅Succeeded View

For more details, please refer to the build report.

For any questions, please:

@@ -11,7 +11,7 @@ ms.localizationpriority: high
>
> SharePoint Embedded copilot is currently in private preview. Stay tuned for latest API and SDK changes on this page.
>
> SPE copilot consumption-based model will soon be available this coming May! Starting May 1st, Standard billing model will be available to all private preview customers, and this roll out is expected to complete by May 15, 2025. This means that starting May 15th, to access SPE copilot within SPE applications, you will need to use standard container type and the copilot interactions, including those from Copilot license users, will be billed to the Azure subscription associated with your Container Type. Learn more about [SharePoint Embedded billing management](/sharepoint/dev/embedded/administration/billing/billingmanagement).
> SPE copilot consumption-based model will be available starting May 2025! Starting May 1st, Standard billing model will be available to all private preview customers, and this roll out is expected to complete by May 15th. This means that starting May 15th, to use SPE copilot within SPE applications, you will need to use standard Container Type and the copilot interactions, including those from Copilot license users, will be billed to the Azure subscription associated with your Container Type. Learn more about [SharePoint Embedded billing management](/sharepoint/dev/embedded/administration/billing/billingmanagement).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should it be "Standard billing model" or "standard"? If "Standard" then "consumption-based" should be "Consumption-based"?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would say "to use SPE copilot within an SPE application"

updated capitalization and minor grammatical changes per Tony's feedback.
Copy link
Contributor

Learn Build status updates of commit 6e2e7be:

✅ Validation status: passed

File Status Preview URL Details
docs/embedded/development/declarative-agent/spe-da.md ✅Succeeded View

For more details, please refer to the build report.

For any questions, please:

updated based on javier & diego's feedback
Copy link
Contributor

Learn Build status updates of commit 5babff3:

✅ Validation status: passed

File Status Preview URL Details
docs/embedded/development/declarative-agent/spe-da.md ✅Succeeded View

For more details, please refer to the build report.

For any questions, please:

@tonchan-msft tonchan-msft self-requested a review May 1, 2025 02:43
@tonchan-msft
Copy link
Contributor

I approved with the condition that comments from Javier and Diego are addressed. Thanks @clalissayi24 !

@clalissayi24 clalissayi24 requested a review from dluces May 1, 2025 15:14
@@ -11,7 +11,9 @@ ms.localizationpriority: high
>
> SharePoint Embedded copilot is currently in private preview. Stay tuned for latest API and SDK changes on this page.
>
> Currently, to use SPE copilot, the consuming tenant user of the application is required to have a [Microsoft 365 Copilot license](/copilot/microsoft-365/microsoft-365-copilot-licensing). In the future, the license-based model will be replaced with a consumption-based model. Stay tuned for billing model announcements during the preview period.
> SPE copilot consumption-based model will be available in May 2025! Starting May 1st, standard billing model will be available to all private preview customers, and this rollout is expected to complete by May 15th. This means that starting May 15th, to use SPE copilot within an SPE application, you will need to use standard Container Type and copilot interactions, including those from Copilot license users, will be billed to the Azure subscription associated with your Container Type. Learn more about [SharePoint Embedded billing management](/sharepoint/dev/embedded/administration/billing/billingmanagement).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

standard billing model do we describe what this is?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cindylay
Copy link
Contributor

cindylay commented May 1, 2025

still one comment to be resolved, see Greg's, but otherwise ready to go

@clalissayi24 clalissayi24 marked this pull request as ready for review May 1, 2025 20:49
@VesaJuvonen VesaJuvonen merged commit 0262e0e into SharePoint:main May 5, 2025
2 checks passed
Copy link

@Classicrichblog Classicrichblog left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approve

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants