Update SPE docs to incorporate new Container Type Management APIs #10336
Conversation
|
Learn Build status updates of commit 56452ff: ✅ Validation status: passed
For more details, please refer to the build report. |
dluces
changed the title
dluces
changed the title
|
Learn Build status updates of commit 20d5452: 💡 Validation status: suggestions
docs/embedded/getting-started/containertypes.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. |
|
Learn Build status updates of commit 96fb02d: 💡 Validation status: suggestions
docs/embedded/getting-started/containertypes.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. |
|
Learn Build status updates of commit bb54408: 💡 Validation status: suggestions
docs/embedded/getting-started/containertypes.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. |
dluces
force-pushed
the
user/dluces/use_ct_mgmt_apis
branch
from
bb54408 to
446825c
Compare
|
Learn Build status updates of commit 446825c: 💡 Validation status: suggestions
docs/embedded/getting-started/containertypes.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. |
dluces
force-pushed
the
user/dluces/use_ct_mgmt_apis
branch
from
0166259 to
5647201
Compare
|
Learn Build status updates of commit 0166259: 💡 Validation status: suggestions
docs/embedded/getting-started/containertypes.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. |
|
Learn Build status updates of commit 5647201: 💡 Validation status: suggestions
docs/embedded/getting-started/containertypes.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. |
|
Learn Build status updates of commit 7b01459: ✅ 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 |
|
Learn Build status updates of commit 5953f03:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| docs/embedded/administration/billing/billing.md | View | Details | |
| docs/embedded/administration/developer-admin/dev-admin.md | View | Details | |
| docs/embedded/getting-started/containertypes.md | View | Details | |
| docs/embedded/administration/billing/meters.md | ✅Succeeded | View | |
| docs/embedded/administration/consuming-tenant-admin/cta.md | ✅Succeeded | View | |
| docs/embedded/development/auth.md | ✅Succeeded | View | |
| docs/embedded/getting-started/register-api-documentation.md | ✅Succeeded | View | |
| docs/embedded/getting-started/spembedded-for-vscode.md | ✅Succeeded | View |
docs/embedded/administration/billing/billing.md
- Line 39, Column 85: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#set-up-billing-for-passthrough-app' in 'embedded/administration/consuming-tenant-admin/cta.md'.
docs/embedded/administration/developer-admin/dev-admin.md
- Line 45, Column 643: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#set-up-billing-for-passthrough-app' in 'embedded/administration/consuming-tenant-admin/cta.md'.
docs/embedded/getting-started/containertypes.md
- Line 40, Column 4: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#standard-container-types-non-trial' in 'embedded/getting-started/containertypes.md', did you mean '#standard-container-types-nontrial'?
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.
| ms.localizationpriority: high | ||
| --- | ||
|
|
||
| # SharePoint Embedded billing | ||
|
|
||
| SharePoint Embedded is a consumption-based Pay-as-you-go (PAYG) offering meaning you pay only for what you use. SharePoint Embedded provides two billing models that the tenant developing the SharePoint Embedded application can select for respective container types, tailoring it to their unique business requirements. The two billing models are Standard and Pass-through billing. | ||
| SharePoint Embedded is a consumption-based pay-as-you-go offering meaning you pay only for what you use. SharePoint Embedded provides two billing models that the tenant developing the SharePoint Embedded application can select for respective container types, tailoring it to their unique business requirements. The two billing models are Standard and Passthrough billing. |
There was a problem hiding this comment.
"when defining their container type"
I think we need to make it clear that once the CT is created the billing model can not be changed
|
|
||
| ### Standard | ||
| ## Standard billing | ||
|
|
||
| With the standard billing model, all consumption-based charges are directly billed to the tenant who owns or develops the application. The admin in the developer tenant must establish a valid billing profile when creating a standard container type. |
There was a problem hiding this comment.
I think we should make a comment that setting up the billing profile is a step to be taken after the CT is created.
"After the CT is created, the admin in the developer tenant...."
| ms.date: 03/03/2025 | ||
| title: Pay-as-you-go billing for SharePoint Embedded | ||
| description: This article explains the billing models and how to set up pay-as-you-go billing. | ||
| ms.date: 08/13/2025 | ||
| ms.localizationpriority: high | ||
| --- | ||
|
|
||
| # SharePoint Embedded billing |
There was a problem hiding this comment.
I'd update this title to
"SharePoint Embedded billing models"
There was a problem hiding this comment.
The title for the "Pay as you go message" doesn't seem related to the description, at least to me.
There was a problem hiding this comment.
In the Egress section, it says that "to the data downloaded from the SharePoint Embedded platform to the customer's client device such as a desktop or mobile device.".
We have to be a bit more careful with this, to also include the case where an SPE service application makes calls that translate into Egress, but doesn't necessarily downloads that data to any end user device.
Category
What's in this Pull Request?
Update SPE docs to point to new Container Type Management APIs on MSGraph instead of powershell cmdlets.