SharePoint Embedded Documentation Taxonomy (SharePoint#10138)

* organize local file hierarchy

* changes to toc.yml and redirect URL links

* fix files at root of directory

* fix files in ./getting-started

* fix all files in ./development including tutorials and content experiences

* fix all files in ./compliance

* fix all files in ./administration including billing, consuming-tenant-admin, and developer-admin

* fix links

* typo

---------

Co-authored-by: Andrew Connell <[email protected]>

Author: cindylay

.openpublishing.redirection.json

@@ -144,6 +144,131 @@
       "source_path": "docs/embedded/terms-of-service.md",
       "redirect_url": "/sharepoint/dev/embedded/overview",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/embedded/concepts/admin-exp/adminrole.md",
+      "redirect_url": "/sharepoint/dev/embedded/administration/adminrole",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/embedded/concepts/admin-exp/billing/billing.md",
+      "redirect_url": "/sharepoint/dev/embedded/administration/billing/billing",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/embedded/concepts/admin-exp/billing/billingmanagement.md",
+      "redirect_url": "/sharepoint/dev/embedded/administration/billing/billingmanagement",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/embedded/concepts/admin-exp/billing/meters.md",
+      "redirect_url": "/sharepoint/dev/embedded/administration/billing/meters",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/embedded/concepts/admin-exp/consuming-tenant-admin/cta.md",
+      "redirect_url": "/sharepoint/dev/embedded/administration/consuming-tenant-admin/cta",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/embedded/concepts/admin-exp/consuming-tenant-admin/ctaUX.md",
+      "redirect_url": "/sharepoint/dev/embedded/administration/consuming-tenant-admin/ctaUX",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/embedded/concepts/admin-exp/consuming-tenant-admin/ctapowershell.md ",
+      "redirect_url": "sharepoint/dev/embedded/administration/consuming-tenant-admin/ctapowershell",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/embedded/concepts/admin-exp/developer-admin/dev-admin.md",
+      "redirect_url": "sharepoint/dev/embedded/administration/developer-admin/dev-admin",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/embedded/concepts/security-and-compliance.md",
+      "redirect_url": "sharepoint/dev/embedded/compliance/security-and-compliance",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/embedded/concepts/app-concepts/app-architecture.md",
+      "redirect_url": "sharepoint/dev/embedded/development/app-architecture",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/embedded/concepts/app-concepts/auth.md",
+      "redirect_url": "sharepoint/dev/embedded/development/auth",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/embedded/concepts/content-experiences/office-experience.md",
+      "redirect_url": "sharepoint/dev/embedded/development/content-experiences/office-experience",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/embedded/concepts/content-experiences/search-content.md",
+      "redirect_url": "sharepoint/dev/embedded/development/content-experiences/search-content",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/embedded/concepts/content-experiences/user-experiences-overview.md",
+      "redirect_url": "sharepoint/dev/embedded/development/content-experiences/user-experiences-overview",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/embedded/concepts/fluid.md",
+      "redirect_url": "sharepoint/dev/embedded/development/fluid",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/embedded/concepts/app-concepts/limits-calling.md",
+      "redirect_url": "sharepoint/dev/embedded/development/limits-calling",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/embedded/concepts/app-concepts/sharing-and-perm.md",
+      "redirect_url": "sharepoint/dev/embedded/development/sharing-and-perm",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/embedded/tutorials/doc-processing-acs.md",
+      "redirect_url": "sharepoint/dev/embedded/development/tutorials/doc-processing-acs",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/embedded/tutorials/launch-experience.md",
+      "redirect_url": "sharepoint/dev/embedded/development/tutorials/launch-experience",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/embedded/tutorials/metadata.md",
+      "redirect_url": "sharepoint/dev/embedded/development/tutorials/metadata",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/embedded/tutorials/migrate-abs-to-spe.md",
+      "redirect_url": "sharepoint/dev/embedded/development/tutorials/migrate-abs-to-spe",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/embedded/tutorials/using-file-preview.md",
+      "redirect_url": "sharepoint/dev/embedded/development/tutorials/using-file-preview",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/embedded/tutorials/using-webhooks.md",
+      "redirect_url": "sharepoint/dev/embedded/development/tutorials/using-webhooks",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/embedded/concepts/app-concepts/containertypes.md",
+      "redirect_url": "sharepoint/dev/embedded/getting-started/containertypes",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/embedded/concepts/app-concepts/register-api-documentation.md",
+      "redirect_url": "sharepoint/dev/embedded/getting-started/register-api-documentation",
+      "redirect_document_id": false
     }
   ]
 }

docs/embedded/concepts/admin-exp/adminrole.md renamed to docs/embedded/administration/adminrole.md

@@ -1,7 +1,7 @@
 ---
 title: PAYG billing for SharePoint Embedded
 description: This article explains the billing models and how to set up PAYG billing.
-ms.date: 02/12/2025
+ms.date: 03/03/2025
 ms.localizationpriority: high
 ---
 
@@ -13,13 +13,13 @@ SharePoint Embedded is a consumption-based Pay-as-you-go (PAYG) offering meaning
 
 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.
 
-![Standard](../../../images/1bill521.png)
+![Standard](../../images/1bill521.png)
 
 ### Pass-through
 
 With pass-through billing, consumption-based charges are billed directly to the tenant registered to use the SharePoint Embedded application. Admins in the developer tenant don't need to set up a billing profile when creating a pass-through SharePoint Embedded container type. Once the container type is registered in the consuming tenant, the consuming tenant admin (SharePoint Admin or Global Admin) needs to set up the billing profile in the consuming tenant to use the SharePoint Embedded application.
 
-![Pass Through](../../../images/2bill521.png)
+![Pass Through](../../images/2bill521.png)
 
 ## Prerequisites to create SharePoint Embedded container type
 
@@ -29,6 +29,14 @@ A new container type will be created using **SharePoint Online Management Shell*
 1. Open SharePoint Online Management Shell from **Start** screen, type **sharepoint**, and then select **SharePoint Online Management Shell**.
 1. Connect to SPO service using `Connect-SPOService` cmdlet by providing admin credentials associated with tenancy. For information on [how to use Connect-SPOService](/powershell/module/sharepoint-online/connect-sposervice), refer the linked documentation.
 
+### Tenant requirements
+
+- An active instance of SharePoint is required in your Microsoft 365 tenant.
+- Users who will be authenticating into SharePoint Embedded Container Types and Containers must be in Entra ID (Members and Guests)
+
+    > [!NOTE]
+    > An Office license is not required to collaborate on Microsoft Office documents stored in a container.
+
 ### Roles and Permissions
 
 - The admin who sets up the billing relationship for SharePoint Embedded needs to have owner or contributor permissions on the Azure subscription.
@@ -44,9 +52,9 @@ For the Standard Billing container type, the developer admin needs to set up:
 
 ## Set up a Standard Billing container type
 
-For standard billed container types, developer admin should set up billing in their tenant. Microsoft 365 SharePoint Embedded Administrator serves as the developer admin. Global Administrators in Microsoft 365 can assign users the SharePoint Embedded Administrator. The Global Administrator role already has all the permissions of the SharePoint Embedded Administrator role. The SharePoint Embedded Admin role is available in Microsoft Entra and Microsoft 365 Admin Center.
+For standard billed container types, developer admins should set up billing in their tenant. The Microsoft 365 SharePoint Embedded Administrator serves as the developer admin. Global Administrators in Microsoft 365 can assign users the SharePoint Embedded Administrator role, which already has all the permissions of the SharePoint Embedded Administrator role. The SharePoint Embedded Admin role is available in Microsoft Entra and Microsoft 365 Admin Center.
 
-SharePoint Embedded Admin can create container type using `New-SPOContainerType` cmdlet by providing an **Azure subscription**, **resource group** associated with the subscription, and a **region**.
+SharePoint Embedded Admin can create a container type using the `New-SPOContainerType` cmdlet by providing an Azure subscription, the resource group associated with the subscription, and a region.
 
 - If you don't have an Azure subscription, you can create one by following the steps here to [create an Azure subscription in your tenancy](/azure/cloud-adoption-framework/ready/azure-best-practices/initial-subscriptions),
 - If you don't have a resource group, you can create one by following the steps here to [create a resource group](/azure/azure-resource-manager/management/manage-resource-groups-portal)
@@ -99,19 +107,19 @@ New-SPOContainerType -ContainerTypeName <ContainerTypeName>
                      -isPassThroughBilling 
 ```
 
-### [Set Up Guide in Consuming Tenant Admin Center](../../admin-exp/consuming-tenant-admin/cta.md#set-up-billing-for-pass-through-app)
+### [Set Up Guide in Consuming Tenant Admin Center](../consuming-tenant-admin/cta.md#set-up-billing-for-pass-through-app)
 
 1. In [Microsoft 365 admin center](https://admin.microsoft.com/), select **Setup**, and the view the **Files and Content** section. Select **Automate Content with Microsoft Syntex.**
 
-    ![Microsoft 365 admin center Files and Content](../../../images/DTCBilling1.png)
+    ![Microsoft 365 admin center Files and Content](../../images/DTCBilling1.png)
 
 1. Select **Go to Syntex settings**.
 1. Select **Apps** under **Syntex services for**, select **SharePoint Embedded**
 
-    ![Microsoft 365 admin center SharePoint Embedded Billing setting](../../../images/DTCBilling2.png)
+    ![Microsoft 365 admin center SharePoint Embedded Billing setting](../../images/DTCBilling2.png)
 
 1. Follow the instructions on the **SharePoint Embedded** flyer to turn on SharePoint Embedded apps.
 
 ## SharePoint Embedded meters
 
-Refer to the [SharePoint Embedded meters](meters.md) article to learn more about the supported pay-as-you-go meters.
+To learn more about the supported pay-as-you-go meters, refer to the [SharePoint Embedded meters](meters.md) article.

docs/embedded/concepts/admin-exp/billing/billing.md renamed to docs/embedded/administration/billing/billing.md

@@ -21,7 +21,7 @@ The Microsoft Cost Management portal provides a comprehensive overview of your c
 1. Once signed in, locate the left-hand navigation menu.
 1. Select on "Cost Management + Billing". If it's not visible, you can search for it using the search bar at the top of the portal.
 
-    ![Cost Management](../../../images/billmanag1.png)
+    ![Cost Management](../../images/billmanag1.png)
 
 ### Select Your Subscription
 
@@ -39,7 +39,7 @@ The Microsoft Cost Management portal provides a comprehensive overview of your c
 1. In the Cost Analysis page, you can customize the date range to view costs for specific periods.
 1. Use the filters to break down costs by tags - app ID, tenant ID or container type ID. Filters can also set by Meters, Resources etc. Refer to the [SharePoint Embedded meters](meters.md) article to learn more about the pay-as-you-go meters supported.
 
-![Meters](../../../images/billmanag2.png)
+![Meters](../../images/billmanag2.png)
 
 ### Download Invoices
 
@@ -51,7 +51,7 @@ The Microsoft Cost Management portal provides a comprehensive overview of your c
 1. To better manage your spending, you can set up budgets and alerts.
 1. Select "Budgets" under the Cost Management section.
 
-    ![Budgets](../../../images/billmanag3.png)
+    ![Budgets](../../images/billmanag3.png)
 
 1. Create a new budget by specifying the amount and the time period.
 1. Set up alerts to notify you when spending approaches or exceeds your budget.

docs/embedded/concepts/admin-exp/billing/billingmanagement.md renamed to docs/embedded/administration/billing/billingmanagement.md

@@ -1,29 +1,24 @@
 ---
 title: SharePoint Embedded Billing Meters
 description: This article describes the meters in SharePoint Embedded.
-ms.date: 05/21/2024
+ms.date: 03/03/2025
 ms.localizationpriority: high
 ---
 
 # SharePoint Embedded Billing Meters
 
-SharePoint Embedded employs a pay-as-you-go (PAYG) billing model through an Azure subscription. Billing is determined by how much data in GB you store in SharePoint Embedded, transactions used to access and modify the container and container contents, and data that is egressed from SharePoint Embedded platform. Each of these factors contributes to the overall cost, ensuring that you only pay for the resources and services you use. You can view this usage and billing details in the [Azure Cost Management](https://ms.portal.azure.com/). Both Standard Billing container type and Pass-through Billing container type will use the same meters.
+SharePoint Embedded employs a pay-as-you-go (PAYG) billing model through an Azure subscription. Billing is determined by how much data in GB you store in SharePoint Embedded, transactions used to access and modify the container and container contents, and data that is egressed from the SharePoint Embedded platform. Each of these factors contributes to the overall cost, ensuring that you only pay for the resources and services you use. You can view this usage and billing details in the [Azure Cost Management](https://ms.portal.azure.com/). Both Standard Billing container type and Pass-through Billing container type will use the same meters.
 
-SharePoint Embedded has three billing meters as shown. Refer to the [product page](https://adoption.microsoft.com/en-us/sharepoint/embedded/) for pricing details 
+SharePoint Embedded has three billing meters as shown. Refer to the [product page](https://adoption.microsoft.com/en-us/sharepoint/embedded/) for pricing details.
 
-|                  SharePoint Embedded Service Meters                          |                      Meter Unit                      |
-| :--------------------------------:   | :----------:       |
-|              Storage                 |   $/GB             |
-|   API Transactions                   | $/Transactions     |
-|           Egress                     |  $/GB              |
 
 ## Storage
 
 Storage consumption meters in SharePoint Embedded apply to the storage used by files and documents along with their metadata and versions. Storage consumption also includes all content in the recycle bin and deleted container collection within SharePoint Embedded.
 
 ## API Transactions
 
-Each Microsoft Graph call made explicitly by the SharePoint Embedded application are counted one transaction and customers are billed based on the transaction count. See the [examples](/graph/api/resources/filestoragecontainer) of Microsoft Graph calls that can be made by a SharePoint Embedded application.
+Each Microsoft Graph call made explicitly by the SharePoint Embedded application is counted as one transaction and customers are billed based on the transaction count. See the [examples](/graph/api/resources/filestoragecontainer) of Microsoft Graph calls that can be made by a SharePoint Embedded application.
 
 However, calls made by internal services to the containers, which the application has no control over, are **not** charged. Some examples of such nonchargeable transactions include: