Microsoft 365 Community Transform SharePoint Add-in model solutions to modern development patterns, 30 Mar 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Transform provider hosted SharePoint add-ins to Azure Active Directory registered applications

Description

This module introduces you to the development of Azure Active Directory registered applications to consume SharePoint Online data as the evolution of SharePoint Add-in model Provider-hosted applications.

This video is part of a series in a playlist about "Transform SharePoint Add-in model solutions to modern development pattern": https://www.youtube.com/playlist?list=PLR9nK3mnD-OXJLA29Q0Xk7psbAUqzQZwe

➡️ Next video on this series - https://www.youtube.com/watch?v=3-fUEd6lGvI&list=PLR9nK3mnD-OXJLA29Q0Xk7psbAUqzQZwe&index=12
⬅️ Previous video on this series - https://www.youtube.com/watch?v=94eJAsAm1Kg&list=PLR9nK3mnD-OXJLA29Q0Xk7psbAUqzQZwe&index=10

#Microsoft365 #MicrosoftGraph #SharePointOnline #ProviderHosted #AzureADApplication

In this video, you will learn about

- Registering Azure AD applications
- Using the current user's security context to access SharePoint Online
- Consuming SharePoint Online data
- Using PnP Framework and AuthenticationManager

📖 All guidance content including code samples can be found here: http://aka.ms/sp/add-in/modernize/samples

✨ Presenter
• Paolo Pialorsi (PiaSys.com)

📃 Agenda
0:00 Introduction
1:29 Transforming from SharePoint Add-in model Provider-hosted app to Azure AD registered application
2:48 Demo
4:25 Overview of generic scaffolded solution
4:53 Configuring security and Dependency Injection
6:25 Sample Azure AD registered application implementation

📝 Learn more
• YouTube playlist for this video series - https://www.youtube.com/playlist?list=PLR9nK3mnD-OXJLA29Q0Xk7psbAUqzQZwe
• Quickstart: Register an application with the Microsoft identity platform - https://learn.microsoft.com/en-us/azure/active-directory/develop/quickstart-register-app
• Tutorial: Register an app with Azure Active Directory - https://learn.microsoft.com/en-us/power-apps/developer/data-platform/walkthrough-register-app-azure-active-directory
• AuthenticationManager class - https://pnp.github.io/pnpframework/api/PnP.Framework.AuthenticationManager.html

💡 Learn more about the Microsoft 365 & Power Platform community
• Microsoft 365 Unified Sample gallery - https://aka.ms/community/samples
• Microsoft 365 & Power Platform Community in YouTube - https://aka.ms/community/videos
• Microsoft 365 & Power Platform - http://aka.ms/community/home

Sharing is caring! You are awesome! 🧡

A

A

Hi there and welcome to this video about upgrading SharePoint provided roasted applications to Azure active directory registered applications. Initial pointerlin model we used to create provider, hosted applications which were application built with whatever development platform of your choice and typically it was.net framework and using in the case of.net framework. The client side of the model or season as well as the rest API, is a for SharePoint online.

A

Typically, a provider hosted application used to consume data in the SharePoint host side of the sharepointed in model Day related to, and could eventually consume data initial Point app site, if any, for your SharePoint adding model solution in the Azure active directory registered applications. On the contrary, you can use whatever technology you like and typically can be something else and not necessarily.net framework.

A

Of course, you can still use.net if you like, can be hosted anywhere and once it has been registered in Azure active directory, you can use it to consume any data of any SharePoint online set collection as long as you have proper permissions to do that as well as you can consume any other workload of micro 365. Thanks to open authorizations and Azure active directory, so from a transformation process point of view, there is no conversion tool to easily upgrade a provided application to an Azure active directory registered application.

A

But at the same time it is quite an easy Journey. You simply need to register an application in Azure ID and to Grant proper permissions to that application, which can eventually be based on the resource, specific consent so that you can Target just specific site collections for your application. Then you will need to get an access token from Azure active directory in order to securely consume the SharePoint rest apis or season or micrograph from within your custom developed solution.

A

And if you are upgrading an already existing.net solution which used to be a provider hosted, and you want to make it as an Azure active directory register application. You can simply replace the logic that you use to get a in context of this. Sharepoint client object model, for example, using the PNP framework, authentication manager class and then all the reminder, part of your code can still be the same as before. So let me move to the little environment, and let me show you how to do that in practice.

A

Imagine that you want to create a web application which will behave like a provider roasted application. You want to register it as an Azure active directory application, and you want to use it to consume content in a SharePoint online site like, for example, this library of documents, so using visual studio. You can, for example, create a new asp.net core web application. You will have to provide a name for your application. This one could be absolutely fine and then you will have to choose a version for the framework.net6 long term. Support is a good one.

A

You should select an authentication type and Microsoft identity platform will be the right one for this scenario, so that you will be able to rely on Azure, active directory and on the Microsoft identity platform for authentication, and then you can click on Create and you will go through the project creation process.

A

As you will see, you will have to provide information about the target Azure active directory tenant. You want to use here. We are using the.net Microsoft identity tool. We have to specify the credential, we want to use to access the target tenant and we can create a new application which can be AED provider hosted demo.

A

For example, in my tenant, I will register the application and I will be able to use this application for authentication while using the web app that I am creating so click on finish and you will have an application ready to go with the program.cs file with all of the settings for the dependency injection configuration of the services to have the authentication and the Microsoft identity web in place, as well as the authorization rules with the default policy and stuff like that, then you will have in the app settings to configure the coordinates of your application is ready, so the domain daily, the client, ID and so on so forth.

A

Now I already have an application that I created for the sake of having a fully working and fully functional demo, and here we are in a web application which I create exactly like the previous one and which I also configured in the building of the services.

A

That I want to enable token acquisition to call Downstream API and to have in-memory token cache, so that I will be able to use access tokens into retrieve access token in an incremental mode inside the implementation of my application and I will use it to get an access token to consume.

A

Sharepoint online as like, as my application, was a old school provider or setup of the SharePoint editing model, and then I also have configured in Azure active directory in the Target and application with this specific client, ID and 10 and ID, which has been configured in the authentication in order to be a web application and right now, I'm using the return URL that I have locally on my development environment. This will be replaced then, with the actual public URL of your application.

A

When you will publish it and then in the API permission, sections I have configured that I want to have some permissions for micrograph and specifically I want to have the all site: dot read delegated permission for SharePoint plus I configured a client secret for my application. So now, if I go back to the web application in Visual Studio code, we can see in the settings that I have all of the information about the application that I just showed you in Azure active directory and clearly here we have the domain.

A

The Talented client delete the secret, which I will refresh right after this recording the Callback URL, as well as the URL of the target side that I want to consume. From my application, then I have the page, the actual page, with the Razer model, where I'm going to show the list of documents that I have in my document Library. How can I do that? Well in the page mode and behind the scenes of the index.html file, I have, first of all to specify that I want to use the authorize for Scopes attribute.

A

This is required to have the incremental content in the UI of my application. Then I have a property, a public property which is a list of document types where document is a record with a title and with a link and then in the on get of my page model. I simply rely on a function that I defined right here, which will use SharePoint online via system using the access token, the delegated access token of the currently connected user.

A

So what I'm doing right here is I'm reading from the settings of my application, the URL of the target site- and this can configuration object- is retrieved by a dependency injection in the Constructor of my model, as well as I use, also an instance of the I token acquisition type so that in my code, I can say: okay, let's get the URL of the site.

A

Let's get the root URL of the SharePoint online Target environment, create a request for a scope for a permission: scope for my tenant, slash all site, dot read this is the syntax. You need to use to build the scope you want to get in the access token and then using the token acquisition.

A

I can get an access token for my user, specifying the Scopes that I'm looking for so that I want to have all site dot read for my target tenant and for the currently connected user, which will be authenticated by the Microsoft identity web infrastructure.

A

Then I need to encrypt actually to protect with the secure string at the access token, so that I will be able to use the authentication manager class of PMP framework, which I referenced in my project and I can create an authentication manager which will rely on that secure the access token, so that I can then say get context through the authentication manager and get back a client context of season that I can use with regular season coder as like, as we used to do in the old school SharePoint admin model provider lost applications.

A

I can get a reference to the library of documents and to all the I items. I can load them in the context and make the execute query async without a try using vpnp framework, extension method and once I've done, that I can go through all of the documents that I, retrieved and I can show them. I can add them in the list of documents that I have in my domain model property called documents so that again I can render them in an unordered list of HTML.

A

So let me run the application. Let me show you the output.

A

Here we are in the web browser we will go through go through the authentication process, and here we are back to my asp.net core application, where I can see the list of documents that I have in my target Library here, you can find additional content if you want to dig more into the topic covered and like always, thank you for watching this video.

A

Thank you, foreign.