With the profile completeness extension we can encourage or force users to fill their profiles. This sample SPFx extension renders a profile completeness score. By clicking the score, user can see the score details as shown below:
Microsoft Graph is the gateway to data and intelligence in Microsoft 365. Microsoft Graph provides a unified programmability model that you can use to take advantage of the tremendous amount of data in Office 365, Enterprise Mobility + Security, and Windows 10.
You can use the Microsoft Graph API to build apps for organizations and consumers that interact with the data of millions of users. With Microsoft Graph, you can connect to a wealth of resources, relationships, and intelligence, all through a single endpoint: https://graph.microsoft.com.
In order to call Graph API you need to have a registered application within Azure Active Directory that has delegated permissions for the API application.
Sign in to your Application Registration Portal(https://apps.dev.microsoft.com).
Click on the “Add an app” button.
Enter the app name and click the “Create” button to proceed further.
Copy Application Id(Client Id) and save it.
Now you need to create the Application Secret. To do so click on the “Generate New Password” button as shown below. Once you click the button a pop-up screen will appear displaying the generated one time password. Copy the password and save it securely. Then click the “Ok” button as shown below.
Add the Microsoft Graph Permission as shown below
Click on the “Save” button to update the changes you made.
Grant Admin Consent
Application permissions are used by apps that run without a signed-in user present; for example, apps that run as background services or daemons. Application permissions can only be consented by an administrator.
To grant admin consent through a URL request:
Construct a request to login.microsoftonline.com with your app configurations and append on &prompt=admin_consent.
After signing in with admin credentials, the app has been granted consent for all users.
If you want your SharePoint add-in to appear in SharePoint Store, you need to submit it to the Seller Dashboard for approval. You can add and save your submission as a draft in your Seller Dashboard account until you’re ready to submit it for approval.
This section lists the steps involved in submitting your SharePoint add-in in the Seller Dashboard.
Add a new app
On the overview page, click on Add a new app button
On the listing type page, select SharePoint add-in and click next
On the overview page, provide the mandatory field details as shown below and click next
On the details page, select the necessary languages and provide the mandatory field details as shown below and click next
If you want to prevent the app purchases, select the countries / regions
To get information about users who acquire your add-in, you can submit lead configuration details for your customer relationship management (CRM) system in the Seller Dashboard.
Choose the pricing model fits your need
Save as Draft or Submit
On your summary page, select EDIT DRAFT and make your changes. Select SUBMIT FOR APPROVAL. After your seller account is approved, you can submit your add-in to the Seller Dashboard. You can make changes at any point before you submit for approval, but during the approval process, you won’t be able to make any changes.
Office 365 Service Communications can only be accessed by any user with global admin or product admin rights (for Exchange, Skype for Business and SharePoint).
Dependencies tied to Office 365 Service, as well as the teams that are accountable for those configuration items
The Office 365 Service Communications API is a REST service that allows us to develop solutions using any web language and hosting environment that supports HTTPS and X.509 certificates. The API relies on Microsoft Azure Active Directory and the OAuth2 protocol for authentication and authorization. To access the API from our application, we will need to first register it in Azure AD and configure it with permissions at the appropriate scope. This will enable our application to request OAuth2 access tokens necessary for calling the API. We can find more information about registering and configuring an application in Azure AD at Office 365 Management APIs getting started.
We can use the Office 365 Service Communications API V2 to access the following data:
Get Services: Get the list of subscribed services.
Get Current Status: Get a real-time view of current and ongoing service incidents and maintenance events
Get Historical Status: Get a historical view of service health, including service incidents and maintenance events.
Get Messages: Find Incident, Planned Maintenance, and Message Center communications.
Note: The Office 365 Service Communications API has been released in preview mode. When the General Announcement of Office 365 Service Communications API was made, the older version of the Service Communications API began a period of deprecation.
Sample Calls using Postman
Provide service health information to partners and endusers.
Encouraging early adoption by endusers
Plan our change and release management strategy for Office 365
Plan our monitoring strategy and tool integration for Office 365
Ensure Service Desk and Incident Management know how to proactively operate and support Office 365 in an end-to-end manner by integrating the tools available into our existing processes
Build intelligent bots to naturally interact with our users on a website, app, Microsoft Teams, Skype and more.
Building Microsoft Teams tab using SharePoint Framework
An application that is running in the background, such as a daemon or service
Sample SharePoint Framework client-side web part for Microsoft Teams Tab illustrating Video Recording using MediaRecorder Web API.
This is an experimental web part. Because this technology’s specification has not stabilized, check the compatibility table for usage in various browsers. Also note that the syntax and behavior of an experimental technology is subject to change in future versions of browsers as the specification changes
The Sentiment Analysis API provided by Microsoft evaluates text input and returns a sentiment score for each document, ranging from 0 (negative) to 1 (positive). This capability is useful for detecting positive and negative sentiment in social media, customer reviews, and discussion forums. In this article I am going to show you how to send the feedback entered in a SharePoint online modern list item to Sentiment Analysis API and update the response back in SharePoint. Also I am going to show how to beautify the Sentiment score with emojis using column formatting feature.
Create a SharePoint list with the following columns
At the top of the list, click Flow, and then click Create a flow.
Select the below flow template from the right-hand panel.
Follow the instructions on the Microsoft Flow site to connect to the list we have created. Credentials will be verified for each service used in the flow. For Office 365 services such as SharePoint and Outlook, connections will be created automatically. The next steps will be performed in the Microsoft Flow designer. The first action displayed, also known as a trigger, will determine how the flow will be started. Additional actions may be added after the first. Each new action will be dependent on the previous action.
Next step is to add an initialize variable action to set the value of the current Item Id.
Create a POST request using a HTTP action. Set the HTTP Method, URI, Headers and Body as shown below:
Note: Login to Azure and get the Ocp-Apim-Subscription-Key. Refer this article for steps.
Now let us parse the sentiment score from the response we received from the HTTP action and save the value in a variable using initialize variable action as shown below
Microsoft Teams is a chat-based workspace that brings together people, conversations, content, and tools for easier collaboration. SharePoint sites include the modern page feature, which allow you to engage the team members with important or interesting stories. Here I am going to show you how to display a SharePoint modern page with in teams as a tab.
I have created a SharePoint modern page as show below:
Set up SharePoint Modern Page in Teams
In Teams, navigate to the team where you want your SharePoint page to appear.
Click the plus sign to add a new tab.
Click on Website
Provide a Tab name and SharePoint Modern page url and click Save. Optionally we can select Post to the channel about this tab check box to communicate this change with the users.
That’s it! Now, every time you visit your team, the newly added tab will appear as part of the teams as shown below
You can use the expand / collapse button to view the content the way you like
I don’t know if you noticed, but the out of the box sharepoint controls such as Suite Bar, Left Navigation, Search Box, Page Title Area and Command Bar are gone within teams.
If you have custom webparts within the page, you can not edit properties of those within teams.
You can not change the web part arrangement sequence within teams.
After upgrading the SQL Server Reporting Service to 2016, the SSRS reports embedded in different applications including SharePoint pages using an iframe tag or page viewer web parts were stopped rendering.
I tried to fix this issue by adding the following entries in the rsreportserver.config but no luck.
The rsreportserver.config file is installed in the following location by default:
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\WebServices\Reporting
In SharePoint there used to be a ‘copy shortcut’ option in the right-click menu on a document. This feature is not available currently. Now we need to go to the share sub-menu to get a link to the document, but what is offered there is the docidredir link, not the full path.
This SPFx extension opens a dialog where the user can see the document full path. The Email Link button helps the user to share the link via default email client.