This post describes an observation of how the copy of this page option will be missing for certain pages in SharePoint Online and how to get around it.
Modern pages are great in SharePoint Online…they look good, are easy to author and can be shared really easily once published. However, there are some quirks to the user experience when creating and copying pages, in particular the copy of this page option.
The issue
In the old days of SharePoint 2010, you could only copy or move pages through site content and structure – unless you used PowerShell. Well nowadays it’s as simple as a couple of clicks from the ribbon:
Press + New
Select copy of this page
Copy of this page option available in SharePoint Online.
Or at least that’s what I thought! The problem occurs with the default homepages within modern SharePoint sites. When you go to try to make a copy of the homepage you will find the option is not available.
Copy of this page option missing from menu.
Workaround
The way I’ve managed to get around this issue is to make a copy of the homepage in the Site Pages library, then rename it to something more meaningful. To do this:
Open the Site Pages library
Select the Home.aspx page
Press Copy to
Leave the copy to location as the Site Pages library > press copy here
Press the three dots next to the copied page > rename
Give your page a new name > press rename
Copy the homepage, then rename it to something more meaningful.
That’s it, you can now work on a copy of the page in the same way you would using the copy of this page option.
SharePoint and knowledge bases have gone hand in hand for many years. If you have been involved with SharePoint for any length of time it is not an uncommon request to be asked to build a knowledge base at some point. With the advent of AI and machine learning within Microsoft 365, plus the introduction of Knowledge & Content Services (formerly Project Cortex), SharePoint Syntex and Microsoft Viva Topics, you may think the need to build a traditional knowledge base has gone the way of the dodo.
Well the pricing of the above services means that my organisation won’t readily adopt these new things, so for now at least continuing to leverage metadata rich lists & libraries will have to suffice! Here’s how I built a knowledge base in SharePoint Online…
Site features
Custom site theme/design
Mega-menu navigation
PnP modern search V3
Custom page templates
Site Pages library with additional metadata
Lookup value lists
Change log list
Web parts used
Image with colour block
Search box
Highlighted content
Image/ text
Page properties (KB articles)
Search results web part
Searh filters web part
Approach
I wanted to leverage the modern page authoring experience for creating pages, as there are several people adding content to the knowledge base (KB). So with that in mind the knowledge base is built around the Site Pages library, using the metadata applied to each knowledge base article to drive dynamic web parts throughout the site such as search, page properties and the highlighted content web part.
Within the KB, all KB articles get categorised by the type of technology, application and product they fall under. These work for my KB as I can fit KB articles within these headings. For example:
KB article: How to fix the sync connection in SharePoint 2010
Technology
Application
Product
Microsoft
SharePoint Server
SharePoint 2010
Site Pages library
As mentioned above, the Site Pages library is the lynchpin to the entire knowledge base. Starting with the Pages library, I created columns to capture additional metadata about each KB article. Here are the columns I created:
Technology: lookup column, values held in custom list Application: lookup column, values held in custom list Product: lookup column, values held in custom list Knowledge Type: choice column Topic: Managed Metadata column Contact: Person or Group
Technology, Application & Product are what drive each view within the Site Pages library. I have created a view for each Technology and Application, which are used for web parts embedded within the relevant pages (for example: Microsoft).
Product is used as a way to formalise the type of KB articles that are created (for example: Procedure), with Topic effectively being a way to tag KB articles with a wider variety of terms to aid searching and filtering.
The only thing I did different is I used a different website to generate my theme which you can use here. This theme generator site allows you to access more of the colours that are used when creating a theme to potentially create a multi-coloured theme. For more information of this check out another great post by Laura Kokkarinen here.
Use a theme generator to create a custom theme for your SharePoint Online site.
Homepage
The homepage of the knowledge base is broken down into three key areas: search, recently added and the browse area.
Search: Search web part as part of the PnP modern search solution V3. Connected to a custom search results page (more information below).
Recently added: Highlighted content web part that only shows pages from this site, filtered by recently added earlier this year.
Browse: Three column section consisting of images, text and button web parts. I used the images from the look book template to get the correct sizing for the images above. When updating the images I noticed they didn’t update immediately which I wrote about how to fix here.
Navigation
The navigation for the KB has been created using the mega menu option within the Change the look > Navigation options. The links have all been created manually for each section, with each link going to either a dedicated page or a view created from the Site Pages library.
Mega menu navigation in the IT KB.
Search
Search web part
The search for the knowledge base is all based on web parts from the PnP modern search solution V3. From the homepage there is a search web part. Before configuring the search web part on the homepage you will need to create and configure the search results page and web part as it is required as a data source. I followed the guidance from the PnP modern search solution documentation to configure the search web part with the following properties:
The search web part configuration on the knowledge base homepage.
Search results
The search results is a dedicated page created within the knowledge base that includes the search box, search results and search filters web parts. The search box web part is configured in exactly the same way as on the homepage and just serves as a consistent way to see your search results and search again if required.
The search results web part has been added to a separate, one-third left section underneath the search box web part shared with the search filters web part. The search results web part has the following settings:
Connect to source: Page environment Page environment’s properties: Search Search: Search query Use a default search query: No Query template: {searchTerms} Path:{Site.URL} FileType=aspx Result source identifier: No Sort order: Created, size Sortable properties: None Connect to a search refiners web part: On Use refiners from this component: Filter Connect to search verticals: Off Enable query rules: On Include personal OneDrive results: Off Selected properties: {searchTerms} Path:{Site.URL} FileType=aspx Refinement filters: None Show paging: On Number of items per page: 30 Number of pages: 4 Hide navigation: No Hide navigation if disabled: Yes Results layout: Simple list
Search filter web part
The search filter web part has been added to the search results page with no additional configuration changes made. Don’t forget (like I did), to get the search filter web part to start to work with your search results, you need to turn it on within the search results web part – under connect to a search refiners web part!
Page templates
I’ve used page templates within the knowledge base to standardise the layout of each KB article. At the time of writing there are only two templates to choose from: an application template or new KB article.
Example KB article page template
The KB article page template includes a page properties web part that shows the Knowledge Type, Contact and Topic.
The layout of each KB article page template is as follows: One-third right section: Text web part (left), Page properties web part (right) One column section: Two text web parts One column section: Two text web parts
How to create a page template
Create or open the page you want to use as your template
Press the down arrow next to the save button > Save as template
Page templates will now appear under saved on this site when creating a new page. Templates are also saved in a “Templates” folder within the Site Pages library.
Create page templates to standardise how knowledge is created.
More information on how to manage and delete templates can be found here.
Issues & next steps
Dependant drop-down lists, Power Apps and the Site Pages library
One area I would like to improve on is including the ability to have dependant drop-downs for Technology, Application and Product when applying metadata to KB articles. When creating the KB, I did work on two ways to achieve this- but they both fell short in the end.
My first attempt was to customise the Site Pages library new and edit forms using Power Apps. I used this article by Microsoft on how to create dependent drop-down lists in a canvas apps as a starting point, but had to make some changes to account for the additional third level of drop-down. Although I got this working within the context of PowerApps, I had to abandon this method as creating new pages in the Site Pages library via Power Apps is not supported. My experience was that once I customised the form in Power Apps, it pretty much broke the Site Pages library. I was unable to create new pages and it would default to an old style wiki page and not let me create modern site pages.
Custom forms for document libraries only supports editing custom metadata. Editing or managing file(s) is not supported.
After this failed, I also tried an older way of doing this by using JQuery and SPServices as described here.
Initially I got this to work too, but it was also a pretty poor solution when working with modern pages as the only way to actually get to the dependent drop-downs was by pressing “Edit all” which took you to the classic version of the edit properties page.
Aside from this, you also have to jump through several hoops to add in the old content editor web part, which are too numerous to describe in this post but have linked to one of them.
There was also a recent change to how classic forms work with modern lists that stopped this method working all together. Although this seems to be resolved, my understanding is you have to set your list to run in the classic experience in order to get this method to work – so I’ve scrapped this too!
I currently have no solution for dependant drop-downs, but am open for suggestions that are low code or relatively easy to implement. Feedback so far from users is that they aren’t all that bothered about it as the process to apply metadata is easy.
Images not updating when refreshing
As I was in the process of updating the KB homepage I noticed that when replacing some of the images or other assets that make up the page, they weren’t visibly updating after a forced browser refresh. I wrote a separate post called how to force images to update in SharePoint Online which details how to resolve this.
Updating the modern search solution
When I began building the KB I deployed what is now version 3 of the modern search solution. Since then the PnP team have created PnP Modern Search V4, I’ve personally decided not to update my search solution as at the time of writing V4 doesn’t support suggested keywords which is a part of my solution.
In this post, we will explore what copy and move options are available for end-users in SharePoint, Microsoft Teams and OneDrive, their limitations and what resolution options are available.
The move and copy features in Microsoft 365 are a welcome addition for anyone used to the pains of moving or copying files in classic versions of SharePoint. Gregory Zelfond has a fantastic write up of how to move and copy documents in SharePoint and OneDrive which gives a great explanation of the move/ copy actions which I would recommend everyone check out.
In the good old days, finding where the copy/move features were in SharePoint of old was a small triumph in of itself. Buried within the bowels of manage content and structure, the move feature looked pretty scary – from the confusing navigation tree to the spinning green wheel of worry as to whether your file was actually being moved or not.
The copy/ move features are much, much better now – mainly the unified user experience across M365 makes it much easier to get to grips with and understand. It is now literally as simple as selecting the files or folders you want to copy/ move > pressing copy/ move and do it…well almost!
An example of how easy it is to move files to a new location in SharePoint Online.
Current limitations
As good as the copy/ move features are now, they do however come with their own limitations. When I initially outlined this post in December 2020, much of the limitations were the same as today, however there was a 2GB limit for each individual file that was being copied/ moved in a single operation.
Later in December 2020, Microsoft announced an increased upload file size limit from 100 GB to 250 GB for SharePoint, Teams and OneDrive. Shortly thereafter the SharePoint limits service description was also updated, seemingly to reflect this change. As of February 2021 the requirements are:
– No more than 100 GB total file size – No more than 30,000 files – Each file must be less than 15 GB
When I first realised the above limitations, I thought a way around it might be to just copy the data from source to a new location using the Migration Manager. This will not work as you are only able to specify one level of folder within a given document library in SharePoint, Teams or OneDrive. If you are required to migrate the data to sub-folders two, three or more levels deep within a document library, the Migration Manager will not be able to complete this.
You can only select a top-level folder from a given document library via the Migration Manager.
Practical example
The requirements above becomes an issue when migrating data at scale in my opinion. For example, with a file server migration – organisations that migrate all their file server data into Microsoft 365 with a view to restructure after the fact, the limitations of these requirements become much more apparent.
The 100 GB total file size limit, as with the no more than 30,000 files could cause issues where file server data is concerned as it will stop data owners being able to move large parts of their data structure to new locations if it exceeds this limit – although you could also argue this is also a good thing!
The increase of the individual file size does make a big difference to the overall picture, but now with a 250GB upload limit it could be even more difficult to move data around in future.
Resolution options
I’ve only been able to come up with one actual way to get around this problem – and once again ShareGate is our friend! Running migrations using the ShareGate desktop app allows you to copy from the relevant sub-folder, or to the relevant sub-folder in the destination – no matter how many levels down it is.
You can copy from and to sub-folders using the ShareGate Desktop App.
Aside from this, the only options would be to either:
Only have a top-level folder structure in the destination, to allow you to use the Migration Manager
Reduce the total size/ number of items being moved to allow you to use the native copy/ move features in M365
This post describes how to update the site logo in a classic SharePoint publishing site, plus how it differs from updating the site logo and thumbnail in modern SharePoint sites.
In older versions of SharePoint Server, such as SharePoint 2010 or 2013, you are able to update the site logo of any site or site collection by opening up the site settings and accessing the title, description and icon settings under look and feel.
I recently migrated a SharePoint Server publishing site into SharePoint Online using the copy structure and content option within ShareGate Desktop. Aside from the migration being bloody brilliant (seriously, everything copies across and works the same! more on this in another post), one thing that didn’t work was the site logo.
Copy structure and content in ShareGate Desktop.
The migrated SharePoint site with broken site logo.
How to update the site logo for classic SharePoint publishing sites in SharePoint Online
So in my earlier example, I’d just migrated a publishing site into SharePoint Online and noticed that the site logo was broken and affecting some of the navigation links of the homepage.
This Microsoft article makes mention of how to change the logo, title and description of your SharePoint site. The article also states that if you don’t see this option, it may be that you don’t have permission to see it – well I’m the primary administrator of said SharePoint site so that isn’t the issue!
I figured out a way around it thanks to trusty old SharePoint URLs. Below is how I got to the page, but if you just want to go straight there just add _layouts/15/prjsetng.aspx to the end of your site URL.
Open your SharePoint Online site
Add _layouts/sitemanager.aspx to the end of your URL
Click on the drop-down icon next to your site collection name > Press General Settings
This is the title, description and logo page as described in the Microsoft article previously. From here you can upload your site logo and save it to update your classic publishing site. It’s also worth noting that once you update the site logo from this location, it will also be visible within the modern elements of your classic publishing site (for example Documents).
How to update the site logo in SharePoint Server
For SharePoint Server, follow the steps below to update the site logo:
Before you begin 💡
Make sure you have saved your site logo in a location that is accessible to all users of your site.
Within your site or site collection > Press site actions > site settings
Under Look and Feel > Press Title, description and icon
Under Logo URL and Description > enter the URL path of your site logo
Press OK
How to update the site logo in modern SharePoint sites
With modern SharePoint sites it is really easy to change the site logo. There are two types of site logo you can change:
Site logo thumbnail – appears in search, on the site card and where ever else a square logo is needed. Recommended size is 48 x 48px
Site logo – appears in the site header, which can be transparent or non-transparent. Recommended size is 64 x 64px
Add a new site logo
Navigate to the modern SharePoint site you wish to add a site logo to
Press the cog icon ⚙️ > Press change the look
Within change the look > Press Header
Scroll down until you see site logo thumbnail and site logo
Press Change on either the site logo thumbnail or the site logo
Select a relevant site logo from your computer and press open
Press Save
If you want to remove a site logo, just open the header > scroll down to the logos and press Remove 🗑️.
This post is to serve as a reference point for all the useful shortcut URLs in SharePoint that help admins and super users get their jobs done much easier.
There are several blog posts by others with these URLs in them, but I wanted to preserve them in my own blog for future generations! Most of these links have come from SharePoint 2010, so if you want them to work in differing versions just add a 14, 15 or 16 after the layouts folder to work in 2010, 2013, 2016 or SharePoint Online.
This is a quick tip for anyone who has noticed when they update images in modern SharePoint sites that they don’t seem to update.
I’ve recently been doing a lot more authoring/ page editing in modern SharePoint and a small quirk I have noticed is around images. Usually, if you update an image and overwrite the original a forced browser refresh (CTRL+F5) does the trick – the image will update to show the newest version.
The problem
I’ve been doing the exact same thing in a SharePoint communication site recently and noticed that the updated image would not display – no matter how many times I force refreshed the browser, no matter which browser I use (I flit between Chrome and Edge Chromium quite a lot). The image(s) were saved in the Site Assets Library, not weren’t checked out either so no reason why they would not display once overwritten.
The image (product, right) doesn’t update to reflect the changes made in SharePoint.
The solution
I’ve found a really simple way to get around this:
Right-click on the image > Open the image in a new tab
Force refresh (CTRL + F5) the image in a new tab
Navigate back to the SharePoint communication site > force refresh (CTRL + F5) again
The image will now be displayed as expected
Opening the image in a new tab or window then force refreshing will update the image on the SharePoint page.
If anyone else has come across this issue, or found any other ways to solve it – let me know in the comments!
In this post we will look at how you can add, edit or remove best bet keywords in classic SharePoint and how to do the same with promoted results in modern SharePoint.
In classic SharePoint you are able to highlight search results you wish to make more prominent by using keywords and best bets. Best bets appear at the top of the search results page with a yellow star ⭐ next to them.
Best bets will appear at the top of the search results page in classic SharePoint.
Keywords and best bets are all managed centrally via the Search keywords under Site Collection Administration section within your top-level site.
How to add keywords in classic SharePoint
A keyword is a definition for common terms or phrases that are used within an organisation. Keywords are what search queries will match to return a keyword result. Before you get started, you must have Site Collection Administrator permissions to manage keywords.
Click the Site Actions menu, choose Site Settings
On the Site Settings page, in the Site Collection Administration section, click Search keywords
On the Manage Keywords page, click Add Keyword
Add Keyword from the Manage Keywords page in classic SharePoint.
Enter the following information for each keyword you create:
Keyword phrase: what the search queries will match to return a keyword result
Synonyms: additional words that users might type when searching for the keyword, separated by semicolons. Synonyms must be shorter or equal to 100 characters
Best bets: the recommended results for the keyword. Best bets will appear in the order listed
Keyword definition: optional text that will appear with the keyword (optional)
Contact: the person to inform when the keyword is past its review date (optional)
Start date: the date you want this keyword to appear in search results
End date: the date you want this keyword to no longer appear in search results (optional, leave blank for no expiry)
Review date: the date you want this keyword to be reviewed by the contact (optional)
How to add a keyword best bet in classic SharePoint.
How to edit/ delete keywords in classic SharePoint
Click the Site Actions menu, choose Site Settings
On the Site Settings page, in the Site Collection Administration section, click Search keywords
Click on the keyword you wish to edit and press Edit. When editing a keyword you are able to update all of the information listed above, plus:
Add additional best bets
Change the properties of a best bet
Change the order of best bets by updating the number of the Title next to the best bet
How to edit keywords in classic SharePoint.
How to delete keywords in classic SharePoint
Click the Site Actions menu, choose Site Settings
On the Site Settings page, in the Site Collection Administration section, click Search keywords
Click on the keyword you wish to delete and press Delete
How to delete keywords in classic SharePoint.
Modern SharePoint
Promoted results
Although a lot has changed with the advent of the modern search experience in SharePoint, you can still create and configure keywords and best bets – now called Promoted Results! Microsoft have published comprehensive guidance on how to manage query rules and add promoted results here, but summarise the steps myself below.
How to add promoted results in modern SharePoint
First you will need to consider whether you want your promoted results to appear across the tenant, a site collection or site within SharePoint before beginning. In this example I am creating a tenant-wide promoted result.
Navigate to the SharePoint admin center > More features > Search. Press Open
Within the search administration page, select Manage Query Rules
Open Manage Query Rules from within the SharePoint admin center.
On the Manage Query Rules page, select a result source for the new query rule (you can change this later)
Select New Query Rule. The new query rule has the following configuration options:
Rule name: enter the name for the new query rule
Context: restrict the rule to queries performed on a particular result source, from a particular category of topic page, or by a user matching a particular user segment
Query Conditions: define when a user’s search box query makes this rule fire. You can specify multiple conditions of different types, or remove all conditions to fire for any query text. Every query condition becomes false if the query is not a simple keyword query, such as if it has quotes, property filters, parentheses, or special operators
Actions: actions can add promoted results above the ranked results, add blocks of additional results promoted to always appear above ranked results or ranked so they only appear if highly relevant, or change ranked results, such as tuning their ordering
Publishing: make the query rule active during a particular time period
Add all the relevant information, then under Actions press Add Promoted Result
Add a Title, URL and Description for your promoted results
Make sure Render the URL as a banner instead of as a hyperlink is checked
Press Save
Create a new Query Rule and Promoted Result in modern SharePoint.
Now, when you search across Microsoft 365, you will be able to see your promoted result!
The newly created promoted result shows across Microsoft 365 search.
How to edit or delete promoted results in modern SharePoint
You can manage your query rules and promoted results through the Manage Query Rules page much like creating a new rule. To edit or delete a query rule/ promoted result:
Navigate to the SharePoint admin center > More features > Search. Press Open
Within the search administration page, select Manage Query Rules
Select the result source for the query rule you wish to edit
Click on the drop-down arrow next to the name of the query rule you want to change. From here you can:
View, edit, copy, delete or make the query rule inactive
If you are deleting a rule, once you press Delete you will be prompted with a message to confirm you want to delete the query rule. Press OK
(this post was written using a SharePoint 2010 environment)
A while ago I was trying to find a way of getting a list of all user profiles that didn’t have a profile picture uploaded. I searched around online a bit and could only find examples that involved writing PowerShell which I thought was way to complicated a thing to do!
So this post will show how you can easily export user profile data from SharePoint, apply some excel filters to find all users without a profile picture.
This method applies to all on-premises versions of SharePoint, but also will work for SharePoint Online.
Get user profile data
To get started, open the Excel desktop app
Press Get Data > From Other Sources > SharePoint List
Enter the root site collection URL for your SharePoint environment
Press OK
Press the From SharePoint List option within Get Data in Excel.Enter your root site collection URL here.
This will open a navigator window, which will display all the available lists within the root site collection.
Scroll down until you find the UserInformationList
Click on it and a preview will load, scroll across the preview and make sure you can see the Picture column
Press Load
Make sure you select the UserInformationList and that the Picture column is visible.
NOTE: at first I was using the Get Data > From Web option but that only brought back the first 30 rows from the UserInformationList.
I didn’t want to increase the view limit as there are thousands of rows to display but I found that the way described doesn’t have that issue.
Now this will take a little while to download all the rows if you have a fair few users, but you’ll see when its finished in the right-hand Queries and Connections pane as it shows you the number of rows downloaded once complete.
Filter your data
The first thing to note about this data is that it does also contain some stuff you wont need. With my list data I noted that I had SharePoint security and domain groups, service accounts and other general use/ non-user accounts listed. Here are some of the filters and logic I applied:
Filter the Picture column to only show blanks
Filter the Content Type column to only show Person
Or filter the ContentTypeID to only show the corresponding Person content type ID
Filter SIPAddress to only show rows with an organisational email address
That’s all there is to it, a pretty quick and super easy way to get a list of all user profiles without a picture 🙂
Azure CDN video caching for SharePoint and OneDrive
Microsoft have introduced improved streaming perofrmance for videos stored in SharePoint and OneDrive. Frequently accessed videos will be streamed from the Azure Content Delivery Network (CDN)closest to the user to optimize the playback experience. At all times data will remain within the Microsoft 365 compliance boundary.
Site owners, members and visitors will now see a Share command when they are viewing a list, even when they do not have any list item selected.
Site owners can grant other users access to the list and can specify whether what permissions to grant. Other users (e.g. site members and visitors) cannot directly grant other users access to the list, but they can use the dialog to send an approval request to site owners if the site is set up to allow access requests (enabled by default).
Several improvements have been made to the image column, including the ability to add an image to a list or library using the list itself or a library form. Also, when users are browsing the list on a mobile device, they will be able to upload an image – including taking a photo with the device’s camera.
Add an image to a list items using the improved Image column capabilities.
When you move a file to a new location in Microsoft 365, you will have the option to continue sharing the file from its new destination. A simple pop-up to confirm and keep moving forward.
The new link match permissions just like the source location and we send your collaborators an e-mail that notifies them that the file has been moved.
When you move a file to a new location in Microsoft 365, you will have the option to continue sharing the file from its new destination.
Made available through the Microsoft Look Book, these SharePoint site templates are designed for schools and universities. Each brings together news, events, highlighted content, quick links and more, pre-configured and designed with a specific scope and audience for a variety of Education scenarios.
SharePoint site template: “School home page” – across several screen sizes.
The new Tasks app in Teams provides a new unified view of tasks and assignments from across Microsoft To Do, Planner, and Outlook, helping you consolidate and prioritize your tasks.
there is also an added, new List view with the ability to edit multiple tasks at once, Graph API and Power Automate integrations, and task publishing capabilities to come.
Microsoft have added new features to Whiteboard in Teams to make it easier to keep the creative process moving forward virtually. You can now quickly add sticky notes to a canvas, making it easier to contribute if you’re using a device without a digital pen.
You can now also move and re-order objects on the canvas through a simple drag and drop gesture.
Stay focused throughout the day with Microsoft Teams. Whether you are free for a quick chat or presenting in a meeting, real time presence increases the accuracy of your status so others know when to reach out.
Meeting recording storage for areas where Stream is not available
A new admin setting will allow you to turn on meeting recordings if Microsoft Stream data residency is not yet in country. If this setting is turned on, Teams meeting recordings will be saved in the data center closest to the region.
Optimised Microsoft Teams Experience for VMware Horizon 8
VMWare Horizon 8 now offers enhanced audio and video experience for Microsoft Teams. The optimization pack helps provide better user experience and improved productivity for those leveraging Microsoft Teams across Horizon virtual desktop (VDI) and published application environments.
First, The Windows collaboration display by Avocor is the world’s first and only Windows collaboration display certified for both Microsoft Teams and Azure.
Avocor’s AVW-6555 provides seamless integration with Microsoft Teams video and audio-conferencing capabilities immediately with a Teams-enabled computer.
Then we have new offerings by Logitech, who now have products that support Microsoft Teams Rooms powered by HP.
Logitech now offers Microsoft Teams Rooms powered by HP.
Skype for Business Online connector consolidating to Teams module
Microsoft are simplifying the Teams administration experience with a single PowerShell module that includes complete management capabilities for Microsoft Teams and Skype for Business Online, by introducing full functionality of Skype for Business Online Connector into the Teams Module.
This means that Skype for Business Online Connector in the Skype for Business Online PowerShell, which has been a separate product that contains many cmdlets needed to manage Microsoft Teams, now has been consolidated into a single PowerShell module.
Microsoft have announced that the Teams App Submission API is now generally available. This new Graph API allows all users at any organization to develop on the platform of their choice and submit their apps into Teams with zero friction.
Teams App Submission API is now generally available.
Roster updates from School Data Sync automatically update the Class Notebook roster
Now, School Data Sync (SDS) updates automatically flow to the OneNote Class Notebook! Previously when SDS made roster updates, they would not happen until the educator went and clicked on the “Class Notebook” tab in the Class Team.
Set channel specific collaboration and content spaces
Available now, educators can set Channels in class teams to create sections in Collaboration Space or Content Library, which is especially helpful for educators who like to use channels as separate units. While in a class team, go to the Class Notebook and click “Manage Notebook” to choose which channel a new Section will go.
This allows the educator to create a “read-only” Content Library or student editable “Collaboration Space” specific to each unit and channel.
Now an educator has the option to set Channels to create sections in Collaboration Space or Content Library.
Now in the OneNote Class Notebook or the Staff Notebook, the “Teacher Only” section group will be enabled by default. This saves some extra clicks for this more private view.
IT admins can leverage communication compliance policies and AI models to automatically detect inappropriate content, then review and choose to delete.
Messaging containing offensive or harassing language and adult, racy, or gory images can be automatically flagged then removed from the Teams chat or channel by the IT Admin. This is not supported in private channels or in communications sent by guest users.
Automatically detect inappropriate messages and choose which ones to remove.
Build an interactive classroom with education apps
There are several third party apps that can be used within Teams to assist in finding ways to keep students engaged and learning throughout the day. All the available apps for engagement, communication, content creation and content & curriculum can be found below.
Prezi Video is an example of one of many apps available for Teams to quickly create engaging live or recorded class presentations.
New lobby setting: only the organizer joins the meeting directly for GCC
A new lobby setting is coming to Teams Meeting Options. We are adding “Only me” as an option to the “Who can bypass lobby?” setting. Once enabled, only the organizer will be able to join the meeting directly. Everyone else, including people from within the same organization, will be sent to the lobby.
New experience for launching instant channel meetings for GCC
Meet Now buttons in Teams channels will have a new home. You will soon find them in the Channel header where you can easily find and launch the meeting.
Improved Teams meeting join launcher experience for GCC
When you click on a Teams meeting join link, you will now see an optimized and improved join experience. You will be prompted with an option to join on the web, download the Teams client, or join with the native Teams client. This will result in faster and more confident meeting join.
New policy to prevent upload of profile picture for GCC, GCC High, and DoD
Teams desktop and web experiences will honor the Outlook on the Web mailbox policy setting that can control whether users are able change their profile pictures. This applies to GCC, GCC High, and DoD tenants.
You can now get information about issues you encounter when working with related tables, entities, controls and components on a form by accessing the Monitoring Tool inside your model driven Power App.
The tool can help identify if the issue you are seeing is designed out of box or is due to a customization in the application and provide details that can help you understand why there are issues. To launch the tool just log into your Dynamics or Model Driven app and add &monitor=true to the end of your URL. This will add an icon onto the app header toolbar. Click on the icon that looks like the one in the circle below.
After making improvements to the cascade assign and delete options last year to reduce timeouts, the Power Apps team are making similar improvements to merge operations.
Just as with assign and delete, merges will happen in the background. When a merge operation is run, if you are on build 9.1.0000.20463 or greater, instead of waiting on the submit screen until the job is completed which can take several minutes, you will instead be informed this will be handled in the background.
Power Apps checker now analyzes modern web syntax (up to ES9)
To ensure Power Apps checker continues to broaden analysis coverage as languages evolve, we recently migrated our web language rules to an ESLint plugin and now offer support for ECMAScript 2018 (ES9) syntax plus ES6 globals.
Power Platform Build Tools now generally available
Now generally available, Power Platform Build Tools allows anyone to setup DevOps for low-code and pro-code application development for Power Apps, Power Automate, Power Virtual Agents and other components supported by CDS solutions.
The GA release also introduces support for Multi Factor Authentication with the introduction of Service Principal Authentication.
On-premises data gateway August 2020 update is now available
The August update for the On-premises data gateway (version 3000.54.8 ) includes an updated version of the Mashup Engine, which will match the Power BI Desktop August update.
This will ensure that the reports that you publish to the Power BI Service and refresh via the Gateway will go through the same query execution logic/run-time as in the latest Power BI Desktop version.
AutoML now supports applying models in PQO Function Browser
Analysts can now apply any Power BI AutoML model to entities in any dataflow in the same workspace using PQO function browser. With this new capability, users don’t need to be an owner of the dataflow that has the model. They can use models created by others in the same workspace.
AutoML now supports applying models in PQO Function Browser.
Header/ navigation improvements in the Power BI Mobile apps
The Power BI team have announced improvements to the navigation in the Power BI mobile apps to make it easier for our users to understand their content hierarchy and to navigate between items quickly, aswell as making it easier to share relevant content with colleagues.
Improvements to the header in Power BI mobile apps.
The Power BI team have added a new tenant setting for Power BI admins to choose if users can create classic workspaces. This helps organizations control workspace creation more effectively and prevent unwanted workspaces from appearing in Power BI when Office 365 groups are created.
Allow Power BI Admins to block classic workspace creation.
Multiple data lakes support inside Dataflows in Power BI
The Power BI team have announced improvements to Azure Data Lake Storage Gen2 (ADLS Gen2) support inside Dataflows in Power BI. This includes support for workspace admins to bring their own ADLS Gen2 account, improvements to the Dataflows connector in Power BI, take ownership support for dataflows using ADLS Gen2 and also minor improvements to detaching from ADLS Gen2.
Multiple data lakes support inside Dataflows in Power BI.
Share and collaborate on your bot with subject matter experts
Power Virtual Agents now allows you to share your bot with your teammates, allowing multiple contributors to edit and manage your bot. Subject matter experts in a team can collaborate together on a bot. For example, a customer support bot can now have different subject matter experts working on refund related topics vs. topics related to membership.
Share and collaborate on your bot with subject matter experts.
One of the most common requests for Power Automate is to enable a way to trigger a flow when a column is modified in SharePoint. That wish has now been answered as the Power Automate team have announced the new “When an item or file is modified” trigger.
The “When an item or file is modified” trigger that lets you filter to just the list or file modifications, making it much simpler to create a flow that’s tuned to the right events.
The new “When an item or file is modified” trigger in Power Automate.
The Power Automate team have announced the new “for a selected message” trigger enables any Teams user to create a custom message action to start a flow from any message in Teams.
July 2020 saw seven new connectors added to the Power Automate platform, with now more than 20 new connectors added to the ecosystem in the last three months!
Provision users to Azure AD from SAP SuccessFactors
With the integration between Azure AD and SAP SuccessFactors, you can now automate user access to applications and resources so that a new hire can be up and running with full access to the necessary applications on day one. The integration also helps you reduce dependencies on IT helpdesk for onboarding and offboarding tasks.
Manage and secure all your SAP apps from Azure AD.
Streamlined process for FastTrack for Microsoft 365
Microsoft have streamlined the process for requesting assistance from FastTrack for Microsoft 365. FastTrack is a benefit that comes with your Microsoft 365 subscription, at no additional cost, for customers with eligible plans of 150+ licenses.
Streamlined process for FastTrack for Microsoft 365.
Recently I came across an issue with a SharePoint 2010 publishing site. The site had a page on it that was being edited and after a series of web parts were added, crashed and would no longer load. An additional issue here was that there wasn’t another, recent version of the page to restore to.
So, in the steps below detail how I was able to access the page using web part maintenance mode and delete the problem web part:
Navigate to the problem page’s URL
At the end of the URL add ?contents=1
This will then open the problem page up in web part maintenance mode. From here you are able to close, restore defaults or delete web parts from your page
NOTE: make sure you page is checked out before trying this else you won’t be able to make any changes.
Select the web part(s) which you think are causing the issue
Now select to either close, reset or delete the web part. I chose delete
A warning message will appear > press OK
Modern SharePoint
When writing this post I wondered if this method of accessing web part maintenance mode still worked for modern SharePoint – the answer was no! When you try to open a modern page using ?contents=1 you get this:
Opening modern SharePoint pages in classic maintenance mode won’t work.
However, after reading this handy article from Microsoft about maintenance for client-side web parts in SharePoint Online I just switched my query to ?maintenancemode=true and it worked!
Modern web parts have there own query to append to the page URL to access maintenance mode.
Different to the classic example, modern web parts when in maintenance mode show summary, manifest and data tabs with information about each web part.
If you wish to delete a web part from this view you will need to edit the page and delete it from there, then republish like in the example below:
Deleting web parts in maintenance mode within a modern SharePoint page.
SharePoint URL’s
There are loads of URL’s that either I can never remember or haven’t come across that are listed here. However I wanted to keep a list of them on my site just for reference:
