Contents
If you have a SharePoint provider hosted add-in running on Azure web services, and it stops working when hosted on a SharePoint page inside a app part (or client web part/add-in), or an iframe, then likely you have hit this issue caused by a change in the default cookie property SameSite.
To restore SharePoint add-in functionality, register the provider-hosted add-ins by using the RegisteredIssuerName value that contains the new realm ID. Then, reapply the add-in permissions for each add-in instance. To repair authentication-related issues that are associated with provider-hosted add-ins and hybrid features, follow these steps:
Why do my SharePoint add-ins stop working?
When you configure hybrid, RealmID is changed to match the tenant ID of your Office365 subscription. This causes add-ins to stop working, as explained in the “Symptoms” section. To restore SharePoint add-in functionality, register the provider-hosted add-ins by using the RegisteredIssuerName value that contains the new realm ID.
What causes SharePoint hybrid features to stop working?
Configuring SharePoint hybrid features for SharePoint 2013 or SharePoint 2016 disrupts server-to-server (S2S) trusts that are created before you configure hybrid features.
How to host a PHA site in azure?
Log into the Azure portal (portal.azure.com) with an account with admin rights on the web app in question. Once you open the App Services and select the web app hosting the PHA site, click on the App Service Editor (Preview).
Navigate to your web application settings in Azure portal. Click on Advanced Tools and click Go (in the red box). In the Kudu screen click Debug console > CMD (in the red box). Type the CD site\\wwwroot command (lower red box) to get the root directory of the web application, and press Enter.
How to update Web config file on Azure web app?
Here is how to update the Web.config file on the live instance of your Azure web app- Navigate to your web application settings in Azure portal. Click on Advanced Tools and click Go (in the red box). In the Kudu screen click Debug console > CMD (in the red box).
Where to host a SharePoint add-in in azure?
You can host a provider-hosted SharePoint Add-in on an Azure web role instead of a web application (whether the web application is on-premises or an Azure website). An Azure web role is, essentially, a website that’s based on Internet Information Services (IIS) and hosted on Azure.
One of the most important questions you need to ask when considering provider-hosted add-ins and how you’ll build them is how the add-in will get authorization to interact with SharePoint. Provider-hosted add-ins give you two choices: the JavaScript cross-domain library and OAuth.
Why are my provider hosted add-ins not working?
The script sets the authentication realm by using the Set-SPAuthenticationRealm cmdlet. After the authentication realm is changed, existing SharePoint add-ins fail to authenticate. This authentication failure occurs because of how provider-hosted add-ins are authorized to access SharePoint.
Can a PHAs be an externally hosted service?
PHAs may include an externally hosted web application, service, database, or SharePoint component. This problem does not exist if you configure hybrid features first, and then deploy provider-hosted add-ins and/or Workflow Manager in a SharePoint 2013 or SharePoint 2016 farm.