Updated Guidance around SharePoint Web Service Identification and Throttling (https://aka.ms/spserviceidentity)

[zplume]

Category

• Question
• Typo
• Bug
• Additional article idea

1. The guidance contains this statement about AppID/AppTitle:

If you have created an application, recommendation is to register and use AppID and AppTitle – This will ensure the best overall experience and best path for any future issue resolution. Include also the User Agent string information as defined in following step.

What is meant by 'use' the appID and appTitle? Is this referring to accessing SharePoint using SharePoint/Azure AD app registration (rather than using .NET CSOM with credentials or JavaScript running on a SharePoint page with no app registration)?

What about SPFx web parts that access SharePoint using REST (including pnp-js-core) or JSOM?

2. When is it appropriate to use ISV vs NONISV?
   Should 3rd party developers extending SharePoint on behalf of a client use NONISV?

3. The guidance contains this statement about JavaScript libraries:

If you are building your own JavaScript libraries, which are used to call SharePoint Online APIs, make sure that you include the User Agent information to your http request and potentially register your web application also as an Application, where suitable.

It's not possible to set the user agent for http requests sent from a browser.
Is this referring to node.js build tooling/server applications/Azure Functions?

4. Are there any plans to update CSOM to make setting the UserAgent simpler?
   Perhaps a userAgent string parameter added to a new ClientContext constructor?

Thanks!

CC: @VesaJuvonen

[paulryan]

Yes, it is not clear how this affects JS application especially those running in the context of a SharePoint page.

[GrahamMcMynn]

When running an SPFX solution the requests are run as the user. There is no appID or appTitle that you can decorate your requests with. That documentation about throttling is targeting users who are using 2013 apps.

[CameronDwyer]

I'm trying to understand this guidance in respect to a standalone application (UWP, WinForms, console etc) accessing SharePoint via .Net CSOM, where there is no registered App in Azure, the code is simply accessing SharePoint with valid user credentials. I'm assuming the AppID/AppTitle to be included in the UserAgent needs to be unique so that some throttling rules can identify the traffic and treat it differently? how do we go about generating a unique code and letting Microsoft know about it in this scenario where there is no App to register in Azure? CC: @VesaJuvonen

[msft-github-bot]

This issue is being closed as part of an issue list cleanup project. Issues with no activity in the past 6 months that aren't tracked by engineering as bugs were closed as part of this inititive. If this is still an issue, please follow the steps outlined to re-open the issue.