Skip to content

Commit aa41fc1

Browse files
authored
Updated file to reflect recent changes made to app only access config in modern term store
1 parent 0062d77 commit aa41fc1

File tree

1 file changed

+1
-4
lines changed

1 file changed

+1
-4
lines changed

docs/solution-guidance/elevated-privileges-in-sharepoint-add-ins.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -41,8 +41,6 @@ You can't use the app-only policy with the following APIs:
4141

4242
* Search
4343

44-
* Taxonomy (this only applies to scenarios that write to the managed metadata service)
45-
4644
To use the app-only policy, you first must grant permissions to the add-in by using appinv.aspx. The following code from AppManifest.xml file shows how to set the app-only policy and the permissions for your add-in.
4745

4846
```xml
@@ -53,8 +51,7 @@ To use the app-only policy, you first must grant permissions to the add-in by us
5351

5452
Using the app-only policy requires that your add-in use either low-trust or high-trust authorization. The policy is not available with the SharePoint cross-___domain JavaScript library, which is a third way of getting authorized access to SharePoint resources.
5553

56-
> [!TIP]
57-
> To allow to use app-only access for writing to Taxonomy Term Store, you'll need to explicitly add `app@sharepoint` identity as a Term Store Administrator in the Taxonomy Term Store administrative user interface. This grants the app-only identity needed permissions for write operations. You do not need to perform this step for read operations.
54+
app@sharepoint permission no longer works in the modern term store user interface. That’s because app@sharepoint permission is no longer required for an app to perform taxonomy write operations, as long as the app is registered in Azure AD with the required resource consents for app-only taxonomy access.
5855

5956
### Low-trust authorization
6057

0 commit comments

Comments
 (0)