Happy Birthday SharePoint (Officially an Adult !)

SharePoint, one of the most loved and widely adopted product of Microsoft turns 18 years today (March 18th 2019).

Since this historical product was officially started as SharePoint Portal Server in 2001, its now 18 years old full grown mature product which still dominates the global enterprise market as Microsoft keeps shipping undeniably innovative features very frequently.

SharePoint Portal Server 2001

SharePoint Online In 2019

This article with the entire history briefed nicely by Microsoft’s Bill Baer is so fascinating to read – https://blogs.technet.microsoft.com/wbaer/2015/02/12/the-sharepoint-journey/ 

Advertisement

Get Started with SharePoint Hub Sites (Part 01-UI)

Hub Sites in SharePoint Online is the new way of organizing your sites. Now what does that mean?

Based on the size of an organization, SharePoint admins create multiple sub sites to classify and organize content which usually aligns with the organization hierarchy (Department wise). There can be Team Sites and communication sites and yet, Hub sites can consist both these under one umbrella to help you relate them together based on any attribute such as Projects, Departments, Division, Region or whatever you have.

Let me put it in a simple way – Hub Sites will now help you to associate team sites and communication sites to provide a common navigational hierarchy, search, Logos and look and feel.

Hub sites allows you to standardize the site hierarchy. More importantly, it brings the consistency across all sites. Following are some of the characteristics of Hub Sites Capability:

Some of the Hub Site characteristics are:

• A Common Top Navigation (Global Navigation)

A common global navigation is maintained across all connected sites of the particular Hub site.

• Consistent Look and Feel

Sub sites inherits their look and feel from the root (Hub site) which allows you to maintain a single branding across all your sites. In a simple term, all sites are associated, which means they resides under one Hub.

• Scoped Enterprise Search

Search acts relevantly here. When you search for something in a Hub site, it performs the search within all the sites of that particular Hub Site.

• Site activities

User activities happens within the associated sites which means, the engagements are specific to an defined area.

• Content Aggregation

Automatically aggregates content and displaying from multiple sites. News Web Part, Sites Web Part and Content Web Part can be used in a Hub Site to aggregate content from the associated sites and display the content on the Hub Site’s home page. This reduces a lot of manual work that developers supposed to do to get this done in the earlier days.

Provisioning a Hub Site:

There are two ways you can create hub sites in SharePoint online (Yes ! for now its only supported in SharePoint online). However, there is no template to create a Hub site so you can’t simply create a one using the “New Site” option. Instead, these are the options you have.

1. Create a New site collection and set it as the Hub site
2. or Promote an existing site as the Hub Site and associate other site collections to it.

A SharePoint Team Site or an Communication Site can be converted in to a Hub Site. Ensure you have the “SharePoint Administrator privilege or above” in Office 365  to perform these changes.

Step 1: Create a Hub Site in SharePoint (New) Admin Center (UI)

To do this using User Interface, log-in to Office 365 and direct to New SharePoint Admin Center –> Click on “Sites” from the left navigation panel –> Active Sites –> Click on “Create”

Pick “Communications” Site template and go for “Topic” Site design (for example). Define the Site owner and Site name etc.. and hit “Finish” to create the site.

Step2: Registering Hub Site in SharePoint

Now we need to register the Hub site we just provisioned. No big deal here ! just follow these steps.

Navigate to the SPO Admin Center –> Click on “Active Sites” and that shows you all the active site collections. Choose the one you just desired as the Hub and “Register as Hub Site” from the Hub Site Dropdown as shown below.

Fill in the name of the Hub and hit “Save” to complete this.

You will notice the status is update in a few seconds for this site.

Customize Hub Site

We now have the Hub Site created, its time to little bit of tweaking to match organizational theming (logo, theme color, navigation etc..). Something similar to following, you can change the Hub site logo, site logo, theme, navigation etc.. so that it will inherit to the site underneath (Associated)

To do this let’s go to the Hub Site –> Click “Gear” Icon on the top –> Hub Site settings.

You also can edit the Hub site navigation that appears on all connected sites based on the central navigation (Hub). These elements shall inherit from the Hub Site to connected sites automatically. Note: When you customize the Hub Site after connecting other sites in, it will take up to 2 hours to apply the changes in the respective associated sites.

Associating Sites to the Hub:

From the SharePoint Online Admin Center, click on the checkbox next to the site collection you want to associate with the hub, then from the Hub site drop-down list choose the “Associate with a hub site” option. From the list of all the hubs you have available in your tenant, choose the one you want to connect to and hit “Save”.

Choose the relevant Hub you want this site to be associated.

You will notice the status of the site is updated in a few seconds.

Option2: You can also connect a site to an Hub Site using the “Site Information” section of the respective site.

In this case, I have a site called “Partner Engagement” and I have opened up that in the browser.

To do this, navigate to the site that you want to associate with the hub. Click on Settings gear Icon –> Select Site Information –> Choose the Hub Site Association and hit “Save”.

You will immediately notice that Hub Site Characteristics have been inherited to the Associated site.

Moving sites across Hub Sites:

Hub Sites offers the flexibility to attach and detach (connect and disconnected in other words) associated sites. For instance, let’s say my organization decides to isolate Project management and the site needs to move from IT department to PM department. We can simply detach the site from this existing hub to a new hub.

Important Notes: However, this method only works for Modern SharePoint experience. Site collections that are in legacy mode won’t have this abilities so consider upgrading your experience soon if you haven’t !

Also, once you connect with an Hub Site, Navigation, Theme and Logos will be inherited automatically (That’s the whole idea !) to the newly connected sites.

• You can’t associate a one Hub Site to another Hub Site (e.g. Hub A –> Hub B are isolated)
• Also, an associated site can only be connected to one Hub Site

Dealing with the Hub Site Navigation:

Connecting a site collection to the Hub site, doesn’t automatically add links to the Top navigation of the hub site. By default, only the link of the Hub Site appears on top. You have to build rest of the Top Navigation manually in the hub sites.

Here is how: Navigate to the Hub Site –> Hover over to Top Navigation area –> Click on Edit –> Click the “+” sign to add a new link.
Click OK and –> Save.

In my case, I am adding an 3rd item to my global navigation of the “Marketing Hub.

A Finished navigation should look like this and it will reflect across all associated sites.

Connected (Associated) Sites will automatically contain a link back to the SharePoint Online hub site. You will also notice that you can’t change the theme of an associated site, because it inherits the theme from the hub site and that’s the whole purpose of this feature.

For instance, have a look at this site “Statistics” of my setup. It now has all the items in the Global Navigation inherited from the Hub.

Site Permissions:

When you connect a site collection to an Hub, it doesn’t impact the permissions of the associated site or the Hub. However, you have to ensure that all users who are going to join sites to the Hub site have appropriate permissions to the Hub, that’s it ! the rest shall remain the same.

Detach an associated site from a Hub:

You can disassociate a site being under a Hub if no longer needed. Your navigation and the logo will be gone after disassociating but the theme shall remain the same as it was inherited from the Hub. You need to manually set it to a different one.

To remove the existing hub site association, go ahead and select “None” in Hub Site association drop down list and Save it, simple as that !

Wish you could use PowerShell to do all these? Follow my article no 02 to get the same thins done via PowerShell.

DISCLAIMER NOTE: This is an enthusiast post and is not sponsored by Microsoft or any other vendor.

Add a button in to a SharePoint List/Library to trigger a Flow (part 01)

Part 01 (This article)

Microsoft Flow together with PowerApps undoubtedly revolutionizing the process automation in modern work places. You may have a Flow attached to a document library or list but there is no easy access to initiate that flow from the list/library itself. People have to dig in a little bit to initiate it and that’s a little bit of time consuming for constant usage.

With this article, we will find out how we can overcome this struggle using a little bit of JSON stuff (Don’t worry about that word, you don’t need to be a developer here). Using the Modern SharePoint capabilities, we can embed a button right in front of every item in a list or library so that people can trigger a Flow right there. New column formatting is a cool out of the box capability to get this done.

Now let’s get this started. First and foremost, you need to have a Flow created in place and have the GUID of it.

We’ll get a Flow created really quick in case if you don’t have one. If you have a Flow already in place, you can skip these basic steps

Open up your SharePoint Library and click on the “Flow” drop down on the ribbon as below. Then go to “Create a Flow”

You’ll see a list of available templates. You can utilize these templates if your requirement matches with them. Or simply feel free to create your own. Thankfully, there are a lot of templates published by Microsoft and the community which you can re-use on various scenarios. Unless the requirement is very specific or you are really keen on creating one your own, there is no point of designing a Flow from the scratch.

I am adding a simple “Request Manager Approval” flow here. Pretty straight forward.

Next, go ahead and check if the flow is added to “My Flows” section. If so, you are good to go.

Now go inside the created Flow by clicking on it and copy the highlighted GUID form the address bar of your browser. We need this for our new Button.

https://asia.flow.microsoft.com/manage/environments/Default-f50d518a-e13c-4359-85f6-ef76484f4c32/flows/e290feff-0013-41f2-97dd-91a37fb84ea0/details

Now to add the button but before that we need a new column for this button. From the list or library, go to the very end horizontally and add a new text column to this list/library.

It should be like below after adding. You can edit this view by dragging and dropping the desired column across the library if you wish to. I’m calling mine “Approval” so it makes scenes for a column contains buttons.

Now, go ahead and format this column. Click on the little arrow on the newly created column and go to format mode.

And paste the JSON code below. replace the GUID using the target flow which you have copied to the clip board.

Here’s the code (you will have it provisioned as you go to format mode itself).

{
  "$schema": "https://developer.microsoft.com/json-schemas/sp/column-formatting.schema.json",
  "elmType": "span",
  "style": {
    "color": "#0078d7"
  },
  "children": [
    {
      "elmType": "span",
      "attributes": {
        "iconName": "Flow"
      }
    },
    {
      "elmType": "button",
      "style": {
        "border": "none",
        "background-color": "transparent",
        "color": "#0078d7",
        "cursor": "pointer"
      },
      "txtContent": "Send to Approval",
      "customRowAction": {
        "action": "executeFlow",
        "actionParams": "{\"id\": \"e290feff-0013-41f2-97dd-91a37fb84ea0\"}"
      }
    }
  ]
}

That’s it and you will immediately notice the button applied to your column. This is how my library looks like after adding the button. It still doesn’t look like a button because of the border, background and colors of it.

Cool thing is ! you can customize the button to look like as you want it to be. Further more, you can also make it a logical button which has a condition behind it. (e.g. – show a button only when an item pending for approval).

Read the part 02 of this article series to further customize the button and apply conditions.

Detailed Microsoft article for this is here

DISCLAIMER NOTE: This is an enthusiast post and is not sponsored by Microsoft or any other vendor.

A great bunch of new features coming soon for SharePoint Modern Experience !

SharePoint product team just revealed news about a fantastic set of modernization features which are planned to release in the 1st quarter 2019. Microsoft been aggressively improving the user experience of SharePoint, OneDrive, in fact the whole Office 365 umbrella for the past few years.

Some of these features are brand new while some are updates for legacy SharePoint capabilities. Nevertheless, each of them looks cool and would definitely great to have. The best thing everyone love about Office 365 is, there is no additional cost for any of these updates. Let’s find out what we are going to get soon.

Bulk Check In/Check Out

Microsoft previously released bulk edit for list and libraries and now with this update you will have the ability to check in/out multiple records/documents at once. Have a look at the following screenshot comes from Chris MacNulty.

Document Sets

Document sets group related documents together with shared metadata, routing and visual experiences. They’ve been available in classic mode previously, and now you can work with them in the modern experience starting March 2019 onwards.

Signal Icons

Isn’t that cool when you have a nice visual cue right next to each file as the status? Here are the new list of status signals that you will soon be able to see in your tenant. There will be more signals and the best news is its not going to just limit to SharePoint but also will be available on OneDrive, Teams, and Office Clients too. Wait no longer than February !

Column Totals

Custom views allow you to add calculated fields, such as totals or averages, to the footer of a group or the entire list. Now, totals will display in the modern view without forcing users back to the classic interface. Totals will also show in the modern web parts for lists and libraries.

Sticky Headers

SharePoint is known to have large repositories. Large lists and libraries always takes a scroll vertically and horizontally. With Sticky headers, you will have the column headers pinned at the top of the scrolling window so it helps you identify list values as you move vertically and horizontally through the view. And ! column headers will also remain in place inside the list/library web parts across any page you have added them.

Add Columns In-between Column

Soon you will be able to add a column in between another columns which cuts off the time it takes to reach the end of the column headers. Again, this will help a lot in wider lists/library views where you have lots of columns added in to. Just hover you mouse on the edge between two columns and you will immediately notice the (+) icon.

Column Drag and Drop

Guess what! You don’t have to dig in and modify the views anymore. Moving a column within a list or a library, simply drag it and drop to where you want it to be. Easier right ?

In a quick note: Microsoft always commits to deliver efficiency, reliability and usability across all products. Feel free to raise you voice if you have any idea you think worth actioning here – https://sharepoint.uservoice.com/forums/329214-sites-and-collaboration

Images: Microsoft (original post is here)

Microsoft Flow in a real world scenario: using Office Quick Parts to fill out documents (Part 01)

Part 01 (This Article)

Yes ! a simple and yet solid Microsoft Flow can be configured to fill-out a Word Document stored in your SharePoint library in conjunction with Quick Parts.

Image Courtesy: brookfieldinstitute

With this blog series, I’m going to demonstrate, how you can utilize legacy and yet famous Office Quick Parts with Microsoft Flow to optimize your content creation!. Well, Quick Parts aren’t new, they have been in Office suite since 2010 but still being famous among content creators due to its usability. 

To get started, you need the following fundamentals:

• Office 365 subscription with SharePoint, MS Flow Capabilities
• A document library to store documents
• Microsoft Office Application Installed in your PC or Mac

Once you have them, simply log in to SharePoint online and open up the desired site. You need a document library to store documents and also relevant fields (metadata) to be created to match our quick parts (Date, Company Name, Project Name etc..).

In my case, I have a simple library with few metadata fields created as below.

Following fields in blue, are our quick parts that we will be linking with the SharePoint library fields. They can be belong to a content type (centralized) or a specific to an library, nevertheless we can use quick parts in a document so that anyone can easily fill them out as part of a process.

Once you have added columns in to the library (much more easier in Modern SharePoint experience!), create a new Word document in that library or if you already have a document, just upload it to the library (just drag and drop). my library is the default “Shared Document” and the columns are “Customer, Project name, Date, Project value”, just four, simple !

Once you have uploaded, open it from Word application as shown below.

From Word, direct to Insert –> Quick Parts –> Document Property –> Choose the desired field/s

Here I’m adding Customer field which looks like below once added.

You have to click on each spot where you want Quick part to be placed and it will insert accordingly. I have added some fields multiple times here which is perfectly fine. Normally, a single field value can be used in various location across a document.

Changes are usually saved automatically. If you notice the save icon on the top bar of Word Application. So just go ahead and close this now.

Let’s head back to our library and get started with building the Flow for this scenario. Its easier to work with any office 365 tool nowadays due to the ultimate UI enhancements Microsoft have recently done.

Click on Flow –> Create a flow, from the Library

You will now be redirected to Flow web site and you must sign in using your O365 account to be able to go ahead from here onwards.

Once you signed in, choose New –> Create from blank from the Microsoft Flow home page. Pretty simple right ?

Type in “Manual” and hit “Enter” to search. Select the “Manually triggered button” as shown below.

Next up, we have to choose our SharePoint action. Type in “Get File Content” and select the highlighted action to proceed.

On the trigger options, Choose appropriate input types to match your fields. Keep in mind that your trigger can be whatever you want it to be, in my scenario, I’m using a manual trigger which is easy for me to demonstrate the use case.

Now to format our input parameters in the trigger. In my case, I’m adding 4 input types (Date, text and number) according to the Quick Parts I have. You can have more or less, inputs based on your story.

Customer: Text Field | Amount: Number | Doc Date: Date | Project: Text

Next up, is to configure our 1st SharePoint action to act as we want. we have to bind our SharePoint library to the flow. Choose the site where you have the library from the dropdown. I am using SharePoint because, in this case that’s is where my data resides, but, you can use various other services such as Salesforce, or PowerApps to bring inputs in to the file. The idea of this post is to demonstrate that how data coming from (anywhere) can be automatically entered in to a Word document.

And select the document library from the listed ones. Leave “Infer Content Type” as Yes as well.

Now let’s add a new action here. Click on “New” and add the Create File SharePoint action as below.

This action will update the file properties when the flow is triggered. Select the Site address and folder path (Library). Define the File name by choosing the appropriate fields as you wish. File content should come from the File Content Action itself.

Once this is done, the Flow so far would look like this. make sure you map the fields properly so you wont have any errors during the first run. A positive first impression is something awesome you know that !!

Then, click on “New” and search for “Update file properties” SharePoint action from the list to add our next action.

In here too, we have to configure some parameters to reflect fields and quick parts appropriately. Choose the same site and libraries and Item ID should be “Item ID” from create file. I am using Customer Name field as the title here but its up to you to have your own choice.

Continue to read part 02

DISCLAIMER NOTE: This is an enthusiast post and is not sponsored by Microsoft or any other vendor.

No-Code column formatting in SharePoint Online

SharePoint Online now offers a simple way of formatting columns even if you don’t have any programming experience. Knowing a bit of JSON would be great indeed because, for now this out of the box capability is limited to few types of columns. Yet, you can use JSON for other types that are not supported out of the box.

There are two ways to apply column formatting:

1. You can apply column formatting to an existing column by selecting the column drop down and choosing column settings –> format this column.
2. Or you can apply column formatting during the creation of the column, or by editing the properties of the column.

Right now formatting works for 3 columns types:

• Yes/No (Boolean)
• Choice
• Date

In this example scenario, I have a simple list with 3 columns and we will use the 2nd approach to apply colors. This list contains few records of events which I would like to apply color formatting based on the status of each record.

There has to be a logic behind the field in order to apply a formatting, hence, it’s obvious that you do not need formatting for every column. e.g. Choice filed always contains multiple values which makes scenes (if value equals true =color the record with Green) whereas in a text field there is no such a logic.

Format section is opened nicely on the right pane. Now it just a matter of choosing the appropriate color for the particular column. Each value of the field can be colored so that the end users can easily recognize the status of the record.

To change the color, simply click on the color pallet icon and choose the color.

In this sample, I have defined Green as completed, Blue for Planning and Pink for Scheduled activities accordingly. This change is applicable for all records of this including the existing and new. Any new records shall impact the color formatting.

Advanced Mode is here. If you have your own JSON, go ahead and paste it here and hit “Save” to publish it.

After formatting the columns, it’s still possible to see the code and tweak it if you’d like. Even for unsupported columns, you can paste your JSON code to apply the formatting even though there is no out of the box formatting available as of now.  Go to list/library settings, and click the name of a column.  Scroll down to see the Column Formatting box.

Limiting SharePoint People Picker field to an specific group of people

People picker is a vital field in SharePoint which allows you to pick a person or a group from your organization’s active directory. With this post I’m going to emphasize one of the out of the box ability of the people picker. We can restrict/limit this field for a specific group or people so that the person who inters data would only able to retrieve set of targeted people within a group (e.g. A sales person can only fetch another coworker in his team).

Firstly you have to have a target group. If you don’t have one, go ahead and get it created and then return to your target List/library and add a new “Person or Group” field by clicking “Add New Column”

Choose the type of it as “Person or Group”

Better to have a meaningful description too, for this field and the selection has to be “People Only“. In the “Choose From” option, select your target group which you have created.

This simply means the person who entering data can only retrieve people within this group. That’s it and you can go ahead and save this change.

Now let’s try to insert a record here. As you can see, even though I have hundreds of users in my AD, I am not able to retrieve any entry here because my target group is empty. Once I add people there only I can retrieve them.

So let’s try to add a user in to the group. I have added myself in to “Internal IT” group.

It comes up as you can see here. Just a matter of saving the record now

That’s it !

Zipped Files Experience in SharePoint

SharePoint online and OneDrive for business now lets you upload and use zipped files. Zipped files such as .zip or .rar works seamlessly in OneDrive and SharePoint even better than in your device. Not necessary to hesitate about having a plugin or client, now do you have to manually extract to explore the content. It’s just simple as clicking on the file and you will have it explored right there.

To try this out simply login to your SharePoint online portal or OneDrive library and upload a zipped file.

Also, if you have a folder structure within a zipped file with multiple folders inside it, you are able to navigate across them back and forth which makes it easier to use.

Find and export the list of users who has not completed About Me section in their Office 365 profile

This is the article 08 in this series.

Having a complete profile in Office365 is not just a benefit for user himself, but for the entire organization which directly impacts on productivity. A finished profile leads to better visibility and eventually results in faster communications across hundreds of thousands of employees in an enterprise setup. Ultimate idea of Office Delve (latest interface of profile comes with more capabilities such as recent activities) is to provide overall insights of a user information and his activities/engagements which makes obvious sense for anyone.

Nevertheless, none of these would be in action unless you have a complete profile with basic details entered in. No matter how much HR would try to push, we still spot a lot of random users who haven’t completed their profiles.

With this short and sweet article series, I’m trying to give you the steps that we followed during the identifying process as requested by our HR. screenshots may differ than our production setup, but you surely will get the point here.

I had to use some PowerShell scripting to get this list out from Office 365 and generate a CSV file for each criteria so that HR can directly reach out to the user via emails and advice to take an action to update the profile on the spot. As a result, we were able to get 100% completeness of profiles across a 5000+ employee organization.

There is no out of the box reporting when it comes to Profile Completeness in Office 365, therefore we have no option other than PowerShell. PowerShell is the ultimate tool for O365 administration, whenever graphical interface has a barrier, hence, make sure you dig around it to understand its capabilities to go beyond.

FINDING USERS WITH EMPTY ABOUT ME SECTION IN THEIR PROFILE (This Article)

In this article I’m trying to explain the steps it takes to find out the users who has not filled “About Me” section in their Office 365 profile (or simply, delve profile).

So here we go, following are the requirements before we get started:

• Azure AD PowerShell Module – download here
• Azure AD Administrator rights
• SharePoint Online Administrator rights
• SharePoint Online PnP Module – Download here

Script steps breakdown:

First and foremost, we need to fetch the Office365 credentials and then connect to both SharePoint Online Admin Centre and Azure Active Directory.

$cred = get-Credential
Connect-AzureAD -Credential $cred
Connect-PnpOnline -Url https://mantoso-admin.sharepoint.com/ -Credentials $cred

Then let’s fetch all users in this tenant, who are internal to the company and that have at least one license assigned to them.

$Users = Get-AzureADUser | Where {$_.UserType -eq 'Member' -and $_.AssignedLicenses -ne $null}

Now to create an empty array in which we will later store the output (user list who has not filled the About me field).

$NoAMUsers = @()

Now we will dig in through each user, and check if they hold a SharePoint profile (This is because About Me field is hosted in SharePoint online, not in Azure AD). If the property exists, and empty, it simply means the About me section has not filled by this user.

foreach ($user in $Users) 
{
    $SPProfile  = Get-PnPUserProfileProperty -Account $user.UserPrincipalName -ErrorAction SilentlyContinue
        if ($SPProfile -ne $null)
        {
          if ($SPProfile.UserProfileProperties.AboutMe -eq "")
            {
               $NoAMUsers += $user
            }
        }
}

And, finally we can export the SharePoint result to a CSV through below part.

$NoAMUsers | Select DisplayName, UserPrincipalName | Export-Csv -Path "C:\Tools\reports\NoAMUsers.csv" -NoTypeInformation

If you need to obtain a similar report on other user criteria’s, here are the other articles of this series which would help you to achieve it.

1. Find and export list of users with no Manager Name set in Office 365 profile:
2. Find and export list of users with no Manager Name set in Office 365 profile:
3. Find and export list of users with no Profile Picture set in Office 365 Account:
4. Find and export list of users with no Birthday set in Office 365 profile:
5. Find and export list of users with no Country set in Office 365 Profile:
6. Find and export list of users with no Department set in Office 365 Profile:
7. Find and export list of users with no Skills Defined in Office 365 profile:
8. Find and export the list of users who has not completed About Me section in their Office 365 profile

DISCLAIMER NOTE: This is an enthusiast post and is not sponsored by Microsoft or any other vendor.

Embedding an Excel Spreadsheet in to a Modern SharePoint Page

You might have noticed that SharePoint no longer offers some of its native features. Excel Web part is one of them which was announced my Microsoft sometimes back. With that, we lost the ability to integrate an Excel sheet in to a SharePoint page using that Web part, however, worry no further because, we still can do the same without it.

With this post, we are going to find out an alternative for this struggle in SharePoint online. We now have fantastic looking, flat and neat pages in SharePoint online, thanks to Microsoft for standardizing the user experience in a better way. Editing pages and organizing items inside them in a much more content oriented manner is no longer a hard job, because there are much more out of the box features in SPO than it supposed to few years ago.

With that in mind, I will go ahead open up my SPO document library to upload my excel spreadsheet which I’m planning to embed in to the page.

After uploading the file, simply click on it to open it from the browser.

Then head on to File –> Share –> Click “Embed”

Now go ahead and copy that embed code from here. There are plenty of preferences for you to customize here as well. You can choose to appear it as you want or even restrict from behaviors when users interacting with it. Dimensions will help you to adjust it right to the page as well. So do not hesitate to check them out and preview it Realtime on the window right pane.

Now let’s go back to SharePoint page which I already have (you can create  anew page and embed it there if you do not want to put it in the home page. In my case I will just embed to the Home page.

Click on “+” button to add a Webpart. You have to add the “Embed” Webpart here.

Once you choose that, you will be prompted with the following screen. nothing much to do here except pasting our embed code we copied from the Excel before. And hit “Publish” to finish it.

You now have an excel sheet nicely embedded to your Modern SharePoint page even though there is no Excel Webpart.