Over a million developers have joined DZone.

Solution of Problem “403 (Forbidden) With SP.RequestExecutor.js”

DZone's Guide to

Solution of Problem “403 (Forbidden) With SP.RequestExecutor.js”

How to solve an error in Office365 and SharePoint.

· Web Dev Zone ·
Free Resource

Learn how error monitoring with Sentry closes the gap between the product team and your customers. With Sentry, you can focus on what you do best: building and scaling software that makes your users’ lives better.

Every day I learn something new about SharePoint.

Today, when I was deploying some apps to Office 365, I came across an interesting situation and wanted to dig in.

I was developing an app that uses a list to retrieve specific items and it was working perfectly in my On-Premise environment.

When I deployed the same app to Office 365 Developer Suite, I received this error in my Chrome’s Developer Tools.. something similar to "403 (Forbidden)" linking "SP.RequestExecutor.js" file.

Well, that ruined me for a second — I didn't expect it at all.

Then after some research I found that: "Tenant" needs to be added as "Read" permission in "ApplicationManifest.xml" configuration.


And, the other problem for me was using the Chrome Browser.When you deploy an app to Office 365, you should always use Internet Explorer as your default browser because by default it lets you select the "Trust-Don’t Trust" option which is needed to run the app which Chrome doesn’t provide.

That's all. If you have come across the same situation, now you know the trick.

What’s the best way to boost the efficiency of your product team and ship with confidence? Check out this ebook to learn how Sentry's real-time error monitoring helps developers stay in their workflow to fix bugs before the user even knows there’s a problem.

sharepoint 2013 ,office 365

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}