You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Workflow-based collaboration, with defined state
28
28
29
29
### Why use SharePoint Embedded instead of SharePoint?
30
30
@@ -35,7 +35,7 @@ Where your application is enabling a business-critical or time sensitive process
35
35
36
36
### Description
37
37
38
-
When building applications on top of SharePoint, it will still be possible for a user with permissions to navigate to the underlying site. Based on their permission level, a user may be able to complete actions in the SharePoint interface that weren't intended by your application, for example changing site settings. These actions may have unintended consequences for your application or content.
38
+
When building applications on top of SharePoint, it will still be possible for a user with permissions to navigate to the underlying site. Based on their permission level, a user might can complete actions in the SharePoint interface that weren't intended by your application, for example changing site settings. These actions might have unintended consequences for your application or content.
39
39
40
40
Because SharePoint Embedded is headless, there's no user interface other than what is provided by your custom application. If you don't supply a method to change content or settings through your application, then it won’t be possible for a user to circumvent this through SharePoint. You have the choice for which collaborative features are available in your application, for example sharing.
41
41
@@ -47,15 +47,15 @@ Because SharePoint Embedded is headless, there's no user interface other than wh
47
47
### Why use SharePoint Embedded instead of SharePoint?
48
48
49
49
- You need the collaborative capabilities of SharePoint, only via a highly customized user interface
50
-
- You're handling highvalue content, where you want to manage risk by removing abilities for a user to discover or alter the content repository
50
+
- You're handling high-value content, where you want to manage risk by removing abilities for a user to discover or alter the content repository
51
51
- All containers for the application can share default sharing settings that are separate from your OneDrive and SharePoint settings
52
52
- Content is logically separated from other Microsoft 365 content
53
53
54
54
## Scenario: Customer facing document upload
55
55
56
56
### Description
57
57
58
-
Your application is aimed at an end customer, either within your organization or externally, who needs to upload a file as part of their interaction. You require a simplified enduser experience in your custom application, along with the Microsoft 365 capabilities of document storage and compliance.
58
+
Your application is aimed at an end customer, either within your organization or externally, who needs to upload a file as part of their interaction. You require a simplified end-user experience in your custom application, along with the Microsoft 365 capabilities of document storage and compliance.
59
59
60
60
Using SharePoint Embedded will support this scenario, while not requiring the users of your application to have access or entitlement to your Microsoft 365 tenant.
Copy file name to clipboardExpand all lines: docs/embedded/concepts/admin-exp/billing.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ ms.localizationpriority: high
9
9
10
10
This document outlines the steps an admin will have to follow to set up billing, evaluate actual and forecast costs, and pay invoices on SharePoint Embedded.
11
11
12
-
SharePoint Embedded will be a consumption based PAYG (Pay-as-you-go) offering from SharePoint Online, which means you'll pay only for what you use. As a Developer admin for SharePoint Embedded, you'll set up billing on a container type using SharePoint Online Management Shell and manage forecast of actual costs and invoices in Microsoft Azure portal.
12
+
SharePoint Embedded will be a consumption based Pay-as-you-go (PAYG) offering from SharePoint Online, which means you'll pay only for what you use. As a Developer admin for SharePoint Embedded, you'll set up billing on a container type using SharePoint Online Management Shell and manage forecast of actual costs and invoices in Microsoft Azure portal.
Copy file name to clipboardExpand all lines: docs/embedded/concepts/admin-exp/cta.md
+27-16Lines changed: 27 additions & 16 deletions
Original file line number
Diff line number
Diff line change
@@ -1,20 +1,21 @@
1
1
---
2
2
title: Consuming Tenant Admin
3
-
description: This article describes the role and responsibilities of Consuming Tenant Admin in SharePoint Embedded
3
+
description: This article describes the role and responsibilities of Consuming Tenant Admin in SharePoint Embedded.
4
4
ms.date: 11/28/2023
5
5
ms.localizationpriority: high
6
6
---
7
+
7
8
# Consuming Tenant Admin
8
9
9
-
The organizations that use the SharePoint Embedded applications on their Microsoft 365(Microsoft 365) tenants are the consuming tenants and the persona that is responsible for managing these applications on their Microsoft 365 tenancy is the consuming tenant administrator. Consuming tenant administrators can perform various administrative actions on the SharePoint Embedded applications registered on their Microsoft 365 tenant and on the Containers that hold the content. They can also manage tenant level configurations and ensure that data is stored in a secure, protected way that meets customers’ business and compliance policies. In this article, we describe the enterprise manageability features that are supported and can be performed by the consuming tenant administrator.
10
+
The organizations that use the SharePoint Embedded applications on their Microsoft 365tenants are the consuming tenants and the persona that is responsible for managing these applications on their Microsoft 365 tenancy is the consuming tenant administrator. Consuming tenant administrators can perform various administrative actions on the SharePoint Embedded applications registered on their Microsoft 365 tenant and on the Containers that hold the content. They can also manage tenant level configurations and ensure that data is stored in a secure, protected way that meets customers’ business and compliance policies. In this article, we describe the enterprise manageability features that are supported and available to the consuming tenant administrator.
10
11
11
12
## 1. Consuming Tenant Admin Role
12
13
13
-
Microsoft 365 SharePoint Administrator serves as the consuming tenant admin. Global Administrators in Microsoft 365 can assign users the SharePoint Administrator. The Global Administrator role already has all the permissions of the SharePoint Administrator role. For information about assigning a user the SharePoint Administrator role, see [Assign admin roles in the Microsoft 365 admin center](/microsoft-365/admin/add-users/assign-admin-roles).
14
+
Microsoft 365 SharePoint Administrator serves as the consuming tenant admin. Global Administrators in Microsoft 365 can assign users the SharePoint Administrator. The Global Administrator role already has all the permissions of the SharePoint Administrator role. For information about assigning a user the SharePoint Administrator role, see [Assign admin roles in the Microsoft 365 admin center](/microsoft-365/admin/add-users/assign-admin-roles).
14
15
15
16
## 2. Administration Tools
16
17
17
-
Consuming tenant admins will be able to manage SharePoint Embedded applications with PowerShell commands using [SharePoint Online Management Shell](/powershell/sharepoint/sharepoint-online/connect-sharepoint-online).
18
+
Consuming tenant admins are able to manage SharePoint Embedded applications with PowerShell commands using [SharePoint Online Management Shell](/powershell/sharepoint/sharepoint-online/connect-sharepoint-online).
18
19
19
20
To get started using PowerShell to manage SharePoint Embedded, you have to install the [SharePoint Online Management Shell](https://www.microsoft.com/download/details.aspx?id=35588) and [connect to SharePoint Online](/powershell/module/sharepoint-online/connect-sposervice).
20
21
@@ -23,9 +24,9 @@ To get started using PowerShell to manage SharePoint Embedded, you have to insta
23
24
24
25
## 3. Application Administration
25
26
26
-
With PowerShell cmdlets, tenant admin can get a list of SharePoint Embedded applications registered in their Microsoft 365 tenancy. They can also view all the applications that have read and/or write access and the level of access to these SharePoint Embedded applications.
27
+
With PowerShell cmdlets, tenant admin can get a list of SharePoint Embedded applications registered in their Microsoft 365 tenancy. They can also view all the applications that have "read" and/or "write" access and the level of access to these SharePoint Embedded applications.
27
28
28
-
The following commands can be used manage SharePoint Embedded applications registered on your Microsoft 365 tenants.
29
+
The following commands can be used to manage SharePoint Embedded applications registered on your Microsoft 365 tenants.
OwningApplicationId is the ID of the SharePoint Embedded application and ApplicationId is the ID of the application that has access to the SharePoint Embedded application. Application Administration cmdlets aren't applicable for Microsoft Loop. For more information about using this command, see [Get-SPOApplication cmdlet](/powershell/module/sharepoint-online/get-spoapplication)
43
+
OwningApplicationId is the ID of the SharePoint Embedded application and ApplicationId is the ID of the application that has access to the SharePoint Embedded application. Application Administration cmdlets aren't applicable for Microsoft Loop. For more information about using this command, see [Get-SPOApplication cmdlet](/powershell/module/sharepoint-online/get-spoapplication).
43
44
44
45
## 4. Container Administration
45
46
46
47
### View Containers
47
48
48
-
Admins can get a list of all the containers for a SharePoint Embedded application using the following commands. This command will list all the active containers within the application.
49
+
Admins can get a list of all the containers for a SharePoint Embedded application using the following commands. This command lists all the active containers within the application.
49
50
50
51
```powershell
51
52
Get-SPOContainer -OwningApplicationId <OwningApplicationId> | FT
@@ -55,7 +56,7 @@ The `OwningApplicationId` is the ID of the SharePoint Embedded application. For
55
56
56
57
### View details of a Container
57
58
58
-
Admins can get the details of a container within an application using the following command. This command will return more details of a container including StorageUsed, Ownership details, SiteURL, Label information etc.
59
+
Admins can get the details of a container within an application using the following command. This command returns more details of a container including StorageUsed, Ownership details, SiteURL, Label information etc.
@@ -65,9 +66,19 @@ Here, the Identity is the ID of the Container. For more information about using
65
66
66
67
### Delete Containers
67
68
68
-
When admins deletes a Container, it's moved into the deleted container collection. A deleted container can be restored from the collection within 93 days. If a container is deleted from the collection, or it exceeds the 93-day retention period, it's permanently deleted. Deleting a container deletes everything within it, including all documents and files.
69
+
Deleting a container can have implications on the functionality of a SharePoint Embedded app, Here are some examples of the potential issues that an application can encounter when deleting a container.
70
+
71
+
- Data Loss: Deleting a container removes all its content. If the SharePoint Embedded application relies on the data stored within the deleted container, the app might no longer function as expected or might lose access to critical information.
72
+
- Broken Links: If the SharePoint Embedded application contains links or references to the deleted container, those links become broken, leading to errors or malfunctioning features within the app.
73
+
- Permissions Issues: Deleting a container can affect permissions settings. If the SharePoint Embedded app relies on specific permissions granted to the deleted container, it might encounter permission issues and fail to function properly.
74
+
75
+
Therefore, it's essential to carefully consider the consequences of deleting a container and ensure that appropriate measures are taken to mitigate any potential issues.
76
+
77
+
### Permanent Deletion
78
+
79
+
When admins delete a Container, it goes into the Recycle Bin. A deleted container can be restored from the Recycle Bin within 93 days. If a container is deleted from the Recycle Bin, or it exceeds the 93-day retention period, it's permanently deleted. Deleting a container deletes everything within it, including all documents and files.
69
80
70
-
Admins should notify the Container owners before you delete a Container so they can move their data to another ___location, and also inform users when the Container will be deleted.
81
+
Admins should notify the Container owners before they delete a Container so they can move their data to another ___location, and also inform users when the Container will be deleted.
71
82
72
83
> [!WARNING]
73
84
> Deleting a container may cause unexpected issues for the SharePoint Embedded application the Container belongs to and may interrupt usage of the application.
SharePoint Online enables admins to manage various tenant-wide settings with the [Set-SPOTenant](/powershell/module/sharepoint-online/set-spotenant) PowerShell command. This command allows administrators to modify global settings that impact the behavior and functionality of SharePoint Online for all users in the organization.
118
+
SharePoint Online enables admins to manage various tenant-wide settings with the [Set-SPOTenant](/powershell/module/sharepoint-online/set-spotenant) PowerShell command. This command allows administrators to modify global settings that affect the behavior and functionality of SharePoint Online for all users in the organization.
108
119
109
120
These tenant-wide settings are also applicable to all SharePoint Embedded applications on the tenant. These settings include conditional access policies, BlockDownloadFileTypePolicy, and SharingCapability to name a few. Learn more about the Set-SPOTenant settings here: [Set-SPOTenant](/powershell/module/sharepoint-online/set-spotenant).
SharePoint Embedded uses Microsoft’s comprehensive compliance and data governance solutions to help organizations manage risks, protect, and govern sensitive data, and respond to regulatory requirements. Security and compliance solutions will work in a similar manner in the SharePoint Embedded platform as they do today in Microsoft 365 platform so that data is stored in a secure, protected way that meets customers’ business and compliance policies while making it easy for Compliance and SharePoint Administrators to enforce critical security and compliance policies on the content. For information on supported security and compliance capabilities, see [Security and Compliance](../security-and-compliance.md).
151
+
SharePoint Embedded uses Microsoft’s comprehensive compliance and data governance solutions to help organizations manage risks, protect, and govern sensitive data, and respond to regulatory requirements. Security and compliance solutions work in a similar manner in the SharePoint Embedded platform as they do today in Microsoft 365 platform so that data is stored in a secure, protected way that meets customers’ business and compliance policies while making it easy for Compliance and SharePoint Administrators to enforce critical security and compliance policies on the content. For information on supported security and compliance capabilities, see [Security and Compliance](../security-and-compliance.md).
OwningApplicationId is the ID of the SharePoint Embedded application. Azure Subscription ID is the ID of the Azure Active Directory profile (Microsoft Entra ID) for billing purposes.
44
+
OwningApplicationId is the ID of the SharePoint Embedded application. Azure Subscription ID is the ID of the Microsoft Entra ID profile for billing purposes.
Copy file name to clipboardExpand all lines: docs/embedded/concepts/app-concepts/app-architecture.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -14,9 +14,9 @@ All files and documents in SharePoint Embedded are stored in Containers. All Con
14
14
## Container Relationship
15
15
16
16
- Every Container Type is owned by one SharePoint Embedded Application
17
-
- Only the app owning a Container Type may create instances of a Container.
17
+
- Only the app owning a Container Type might create instances of a Container.
18
18
- Container instances must belong to a Container Type.
19
-
- An app may instantiate zero or more Container instances for a given Container Type.
19
+
- An app might instantiate zero or more Container instances for a given Container Type.
20
20
- Apps can grant permission to other apps to create, read, update, and/or delete Container instances of Container Types of the owning app, for example, to allow backup/restore or DLP apps to operate on content in those Containers and/or create instances of the Container Type. Note, the owning application is charged for storage in all instances of a Container Type regardless of which app originally instantiated the Container.
21
21
22
22
## SharePoint Embedded Containers and Container Types
0 commit comments