SharePoint Add-in model retired - What you need to know!

Поделиться
HTML-код
  • Опубликовано: 21 окт 2024

Комментарии • 18

  • @Andrew_Connell
    @Andrew_Connell  4 месяца назад

    I scour all the Microsoft & community resources so YOU DON'T HAVE TO. Save time & stay informed. Each issue contains all the news you need in less than 5 minutes every other Tuesday plus my insights & guidance on a trending topic. Subscribe to my bi-weekly newsletter & join 9,000+ fellow M365 developers! vtns.io/ytvnewsletter! No clickbait · 100% free · unsubscribe anytime.

  • @MonoDeLaion
    @MonoDeLaion 8 месяцев назад +1

    Hello, congratulations for your excellent content!
    A question regarding the operation of my solutions created with Sharepoint Framework.
    I have my sharepoint app catalog where I load the .sppkg files of my solution.
    Wouldn't this work anymore?
    How would I upload my .sppkg files so I can use them as an application on sharepoint sites?
    Thank you.

    • @Andrew_Connell
      @Andrew_Connell  8 месяцев назад +1

      This retirement has zero impact on the SharePoint Framework... it's only applicable to the SharePoint Add-in model. In fact, you'd mostly likely migrate your existing SharePoint Add-ins to new SharePoint Framework solutions.

  • @SaleenJ
    @SaleenJ 5 месяцев назад

    Andrew, I have a clarification, will Provider Hosted APPs (not Add-Ins), using appreg and appredirect implicit flow be affected? This is different than Provider Hosted Add-Ins.. Its used primarily for Auth flow into your custom web app in order to enable CSOM/Rest calls. I was paying close attention to the words and definitions in the video and still had this question. Also as a side note, Sites.Selected has a major issue with not able to do search queries(KQL) against those collections, FYI.

    • @Andrew_Connell
      @Andrew_Connell  5 месяцев назад +1

      Yup… the appregnew page uses ACS, and that’s also being retired.
      And all infrastructure that implements all add-ins, including provider hosted, will be shut down.
      Sites.Selected didn’t support KQL queries because originally it only did app-only… that would bypass all security trimming. Search doesn’t support app-only scenarios, so it’s not a Sites.Selected issue.
      But Microsoft added support for delegated permissions with Sites.Selected in the last few months.

    • @SaleenJ
      @SaleenJ 5 месяцев назад

      @@Andrew_Connell thank you very much

  • @disgustedluigi
    @disgustedluigi 10 месяцев назад +1

    This is probably a dumb question, but since I’m new to using SharePoint: does this only apply to custom built add-ins or does this affect all existing Sharepoint web parts? Their documentation keeps mentioning web parts but aren’t clear what that exactly entails. I’m trying to get my company to use Sharepoint to send our monthly newsletters, post photos of company events, create a knowledge base of guides and HR information, etc. Will all of these built-in web parts and Sharepoint functionality also be retired? Or are they just talking about custom apps and stuff like webhooks and whatnot? Thanks.

    • @Andrew_Connell
      @Andrew_Connell  10 месяцев назад +1

      This applies to all Add-ins, even those that Microsoft created. Assuming you're referring to SharePoint Online, all web parts in the modern experiences have been rebuilt using the SharePoint Framework, so you should be fine.

    • @disgustedluigi
      @disgustedluigi 10 месяцев назад

      @@Andrew_Connell thanks. yes, I’m building Sharepoint online communication sites using the modern experience. I haven’t developed or used any 3rd party add-ins. So all of those Microsoft add-ins like News or People have already been rebuilt using framework and I don’t need to do anything to make sure these sites keep working? What about applications for Teams? Again, I’m not too experienced with stuff like this yet, so I appreciate the feedback.

    • @Andrew_Connell
      @Andrew_Connell  10 месяцев назад +2

      _> "So all of those Microsoft add-ins like News or People have already been rebuilt using framework and I don’t need to do anything to make sure these sites keep working?"_
      Correct, nothing for you to do.
      _> "What about applications for Teams?"_
      Not sure I understand what you're asking here... Add-ins have nothing to with Microsoft Teams. Add-ins were limited to SharePoint so there's zero chance you have an Add-in in Teams that you need to be concerned about.

    • @disgustedluigi
      @disgustedluigi 10 месяцев назад +1

      @@Andrew_Connell awesome, you’re the best.

  • @UltraL2M
    @UltraL2M 8 месяцев назад

    Thanks for an awesome coverage of this topic. Sorry if it's a repetitive question but after 2026 the app catalogs for tenant / local site will still be available right?

    • @Andrew_Connell
      @Andrew_Connell  8 месяцев назад

      Nothing changes with app catalogs, either tenant or site collection scoped. In fact, that's what's used to deploy SharePoint Framework solutions.

  • @ElizabethOyer
    @ElizabethOyer 3 месяца назад

    Ok -- user side question here. I rely on Add-Ins and the catalog for different functions that are not natively available. Where do I find these types of options in the new framework? Thank you!

    • @Andrew_Connell
      @Andrew_Connell  3 месяца назад +1

      Hmmm... can you help me better understand your question.
      When you say: "...the catalog for different functions that aren't natively available"?
      Do you mean you use SharePoint Add-ins to perform tasks that SharePoint doesn't do out of the box and you're looking for customizations? And if so, you're asking how to find similar customizations that are built using the SharePoint Framework and available in the app catalogs (ie: SharePoint store)?

  • @somnathsingh6277
    @somnathsingh6277 8 месяцев назад

    Hi Andrew,
    Thank you for this content.
    Regarding AadHTTPClient from SPFx webpart, can we use it to call a secured azure custom API that connects to Azure SQL?

    • @Andrew_Connell
      @Andrew_Connell  8 месяцев назад

      Yes... the AadHttpClient API that's part of the SharePoint Framework is used to obtain an access token via SharePoint Online that can be used to access any Microsoft Entra ID (aka: Azure AD) secured endpoint. These could be existing endpoints (like Microsoft Graph, although there's a SPFx API for that as well) or your own custom endpoints (like Azure Functions).
      In fact, I teach exactly this in my course, Mastering the SharePoint Framework (www.voitanos.io/course-master-sharepoint-framework/). I show how to use the AadHttpClient to connect to a secured Azure Function or the Microsoft Graph.