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
title: Modernizing your SharePoint add-in model implementations in Microsoft 365
3
3
description:
4
-
ms.date: 08/28/2023
4
+
ms.date: 09/12/2023
5
5
ms.prod: sharepoint
6
6
ms.localizationpriority: high
7
-
---
7
+
---
8
+
9
+
# Modernization guidance for existing SharePoint add-in model implementations in Microsoft 365
10
+
11
+
SharePoint add-in model was introduced as part of the SharePoint 2013 timeframe and it was also provided as an extensibility option for SharePoint Online (Microsoft 365). While SharePoint add-in model is currently still supported in the SharePoint Online, model and patterns and outdated and are not recommended to be used.
12
+
13
+
Microsoft is looking into officially deprecating SharePoint add-in model in autumn 2023 - spring 2024 timeframe with clear communications on the detailed end-of-life schedule for related features.
14
+
15
+
> [!IMPORTANT]
16
+
> Deprecation means official statement that the feature is no longer being invested, but it's stil supported. End-of-life means that the feature will be discontinued and is no longer available for use.
17
+
18
+
These upcoming changes will be impacting SharePoint add-in model and also authentication patterns using the classic [SharePoint Online hosted Microsoft Azure Access Control Service](https://learn.microsoft.com/en-us/sharepoint/dev/sp-add-ins/authorization-code-oauth-flow-for-sharepoint-add-ins) (ACS) authentication patterns, used with the provided hosted add-ins and potentially with other unattended services connecting to SharePoint Online.
19
+
20
+
## Transformation technologies
21
+
22
+
Here's a high level table of the feature mapping as the add-in model implementation is transformed to use other long term supported features:
23
+
24
+
25
+
26
+
## Transformation guidance for the add-in techniques
27
+
28
+
Here's a list of all articles for the transformation guidance when moving away on using SharePoint add-in model, grouped based on the covered topic:
29
+
30
+
31
+
* Modern Provisioning
32
+
*[Modern provisioning of artifacts and Information Architecture](./Modern-Provisioning.md)
33
+
* Modern Authentication and Authorization
34
+
*[Understanding Azure Active Directory and OAuth 2.0 in the context of SharePoint Online modern development](./Understanding-AAD-and-OAuth-for-SPO-modern.md)
35
+
*[From Access Control Service applications to Azure Active Directory applications](./From-ACS-to-AAD-apps.md)
36
+
*[Building Multi-tenant applications for SharePoint Online](./Multi-tenant-applications.md)
37
+
*[Understanding Resource Specific Consent (RSC)](./Understanding-RSC-for-MSGraph-and-SharePoint-Online.md)
38
+
* Customizing the modern UI
39
+
*[From App Parts and classic Web Parts to modern client-side SPFx Web Parts](./From-App-Parts-to-Modern-Web-Parts.md)
40
+
*[From UI Extensions to SPFx List View Command Set](./From-UI-Extensions-to-ListView-Command-Sets.md)
41
+
*[From status bars and notifications to SPFx Application Customizers](./From-Notifications-to-Application-Customizers.md)
42
+
*[From classic dialogs to modern dialogs with SharePoint Framework](./From-classic-Dialogs-to-modern-Dialogs.md)
43
+
* Building modern SharePoint Online or Microsoft 365 solutions
44
+
*[From SharePoint JavaScript Object Model to Client-side code and PnPjs](./From-JSOM-to-Client-Side.md)
45
+
*[From Client Side Object Model (CSOM) to PnP Framework and PnP Core SDK](./From-CSOM-to-PnP-Libraries.md)
46
+
*[From XSLT rendering to List Formatting](./From-XSLT-to-List-Formatting.md)
47
+
*[From Remote Event Receivers to SharePoint Online Webhooks and Microsoft Graph Webhooks](./From-Remote-Event-Receivers-to-Webhooks.md)
48
+
*[From SharePoint-hosted apps to client-side applications](./From-SharePoint-Hosted-to-Client-Side.md)
49
+
*[From provider-hosted apps to AAD applications](./From-Provider-Hosted-to-AAD-applications.md)
50
+
*[From SharePoint Add-in model Workflow Apps to Microsoft Power Automate](./From-Workflow-Apps-to-Power-Automate.md)
51
+
*[Publishing modern SharePoint applications on Microsoft AppSource](./Publishing-modern-SharePoint-apps-on-AppSource.md)
52
+
53
+
If some essential guidance is not included, please open an issue at the SharePoint developer documentation and we will try to help you as fast as possible with your specific question.
This release focuses on new features within the Viva Connections side and evolving existing capabilities within the other areas on building Microsoft 365 solutions with SharePoint Framework.
### Ability to detect host's theme for Viva Connections Mobile
158
156
159
-
Starting with this version developers have access to `hostContext` in the `AdaptiveCardExtensionContext` object. This property allows to detect host's theme.
157
+
Starting with this version, developers have access to `hostContext` in the `AdaptiveCardExtensionContext` object. This property allows to detect host's theme.
Starting this version React templates use Fluent UI React v8 instead of v7.
175
+
Starting from this version, React templates use Fluent UI React v8 instead of v7.
178
176
179
177
### Transparent outline icon for Teams-hosted web parts
180
178
181
-
The default outline icon for Teams-hosted web parts is now transparent. This allows to meet the Teams design guidelines for application.
179
+
The default outline icon for Microsoft Teamshosted web parts is now transparent. This ensures that the default icon meets the Microsoft Teams design requirements for application.
182
180
183
181
### TypeScript v4.7 Support
184
182
185
183
SPFx solutions now support TypeScript v4.7.
186
184
187
-
### NodeJS v18 support
188
-
189
-
SPFx solutions now support NodeJS v18.
190
-
191
185
> [!NOTE]
192
186
> A developer needs to manually set NODE_OPTIONS environment variable to `--openssl-legacy-provider` to use NodeJS v18 after the NodeJS 18 has been installed. This requirement is intended to be removed with the General Availability version of the 1.18. This setting is required to adjust the toolchain to work properly with Webpack 4 which the SPFx tooling is using for now.
193
187
> This can be done using `export NODE_OPTIONS=--openssl-legacy-provider` on Mac/Linux or `set NODE_OPTIONS=--openssl-legacy-provider` on Windows.
194
188
195
-
196
189
## Deprecations
197
190
198
191
-`BaseAdaptiveCardView` - use `BaseAdaptiveCardQuickView` instead
199
192
-`template` property in `BaseTemplateCardView` and its descendants
200
193
201
194
## Fixed Issues
202
195
203
-
-[#9010](https://github.com/SharePoint/sp-dev-docs/issues/9010) - Placeholder `{tenantDomain}`is not replaced with `SPFX_SERVE_TENANT_DOMAIN`.
196
+
-[#9010](https://github.com/SharePoint/sp-dev-docs/issues/9010) - Placeholder `{tenantDomain}`isn't replaced with `SPFX_SERVE_TENANT_DOMAIN`.
204
197
205
198
## Feedback and issues
206
199
207
-
We are interested on your feedback around the release. Please do let us know any findings or other feedback using the [SPFx issue list](https://github.com/SharePoint/sp-dev-docs/issues).
200
+
We're interested on your feedback around the release. Do let us know any findings or other feedback using the [SPFx issue list](https://github.com/SharePoint/sp-dev-docs/issues).
0 commit comments