# SharePoint Online Integration Component for Platform 24.1

**URL:** <https://forums.pega.com/t/sharepoint-online-integration-component-for-platform-24-1/7825>\
**Category:** General\
**Tags:** 24-1-1, cross-industry, data-integration, lead-system-architect\
**Created:** [July 18, 2024, 10:21am UTC](https://forums.pega.com/t/sharepoint-online-integration-component-for-platform-24-1/7825 "2024-07-18T10:21:16Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![andwww](https://avatars.discourse-cdn.com/v4/letter/a/f19dbf/32.png) [@andwww](https://forums.pega.com/u/andwww)\
**Post date:** [July 18, 2024, 10:21am UTC](https://forums.pega.com/t/sharepoint-online-integration-component-for-platform-24-1/7825/1 "2024-07-18T10:21:16Z")

</div>

The SharePoint Online Integration component on Pega Marketplace does not list Pega Platform '24.1 as a compatible version. Can someone please confirm whether the Marketplace listing needs updating or whether there is a different component for '24.1?

---

<div class="post-metadata">

**Author:** ![andwww](https://avatars.discourse-cdn.com/v4/letter/a/f19dbf/32.png) [@andwww](https://forums.pega.com/u/andwww)\
**Post date:** [July 22, 2024, 10:17am UTC](https://forums.pega.com/t/sharepoint-online-integration-component-for-platform-24-1/7825/2 "2024-07-22T10:17:40Z")

</div>

@andwwwI’ll raise this as a support ticket

---

<div class="post-metadata">

**Author:** ![MarijeSchillern](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/marijeschillern/32/23321_2.png) [@MarijeSchillern](https://forums.pega.com/u/MarijeSchillern)\
**Post date:** [July 22, 2024, 1:46pm UTC](https://forums.pega.com/t/sharepoint-online-integration-component-for-platform-24-1/7825/3 "2024-07-22T13:46:45Z")

</div>

@chans19 could you provide some input?

I was able to find mention of _SharePoint Online Integration_ in the '24 [documentation](https://docs.pega.com/search?labelkey=24&labelkey=platform&personalize=true&q=sharepoint), which does not tally with the Marketplace summary which shows only these versions:

 ![ASF.png](https://pega1.discourse-cdn.com/pega/original/2X/1/1f1acc64347baed7730a3b50d9641d5831eb04a5.png)

[Sourcing attachments from external storage](https://docs.pega.com/bundle/platform/page/platform/case-management/sourcing-attachments-external-storage.html)

[Integrating SharePoint Online with](https://docs.pega.com/bundle/platform/page/platform/data-integration/integrating-sharepoint-online-pega-platform.html)

---

<div class="post-metadata">

**Author:** ![andwww](https://avatars.discourse-cdn.com/v4/letter/a/f19dbf/32.png) [@andwww](https://forums.pega.com/u/andwww)\
**Post date:** [July 24, 2024, 8:38am UTC](https://forums.pega.com/t/sharepoint-online-integration-component-for-platform-24-1/7825/4 "2024-07-24T08:38:13Z")

</div>

The response from Pega Support was:

_Current component uses authentication API that will no longer be working after 1st of November (Azure update). Therefore we have a request to change the authentication means to fulfil this requirement - i.e. development in progress._

@chans19 Does this mean that the component will work now and until November 1st? And on November 1st it will stop working unless the new component is deployed - when will the new component be available?

---

<div class="post-metadata">

**Author:** ![MarijeSchillern](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/marijeschillern/32/23321_2.png) [@MarijeSchillern](https://forums.pega.com/u/MarijeSchillern)\
**Post date:** [July 31, 2024, 11:04am UTC](https://forums.pega.com/t/sharepoint-online-integration-component-for-platform-24-1/7825/5 "2024-07-31T11:04:29Z")

</div>

@andwww the description summary of the Marketplace component [SharePoint Online Integration](https://community.pega.com/marketplace/integration-connector/sharepoint-online-integration) has now been updated to reflect:

• This is compatible with higher versions

• new upcoming version will contain the authentication method change

• existing integration using this component will be affected by Azure change

I have been informed that the component should work for existing tenants but that there are plans to publish a new component designed to support this upgrade to Azure AD (EPIC-94461). This will be at a later date.

In the meantime we are working on a document outlining how to get around the ACS authentication end-of-life issue (US-630908). Once the design is finalized, we will publish the document with all the steps needed for authentication. This would be the alternative approach before it stops working.

At the moment we are unable to provide you with a timeframe.

cc @chans19 @nvkap
