— Julie Turner @SympraxisC @M365pnpjs (@jfj1997) June 20, 2019
This featured in Episode 44 of the SharePoint Dev Weekly podcast.
I’ve been working on a modern intranet project amongst over projects for the last 12-months. This has been more about the transformation of content and business processes, rethinking information architecture and reimagining a modern intranet than it has been about custom development.
I’ve been working on a modern intranet project amongst over projects for the last 12-months. This has been more about the transformation of content and business processes, rethinking information architecture and reimagining a modern intranet than it has been about custom development.
We’ve recently been testing variations in the design of a homepage with different audiences. This side-by-side comparison has allowed end-user feedback, performance and accessibility testing. The same approach has also been useful for previewing and testing the capabilities of new features (like the new Yammer web part). The challenge comes when you need to promote or switch over one of these variations as the new site homepage. The homepage is the page users are directed to when first navigating to a site or clicking on the site logo. It is like as important as the index.html or default.aspx page existence to a website. Note that these variations of the homepage permit testing of content and not site configuration. To test navigation, theme or similar we have separate sites and environments for this purpose.
To solve the problem switching the homepage from an existing page whilst preserving the home.aspx page name I’ve leveraged the SharePoint Pnp cmdlets to create a script that will rename or remove the current homepage (and can remove it through a toggle) and then rename an existing page to make it the new homepage.
Demonstration of the Set-SPNewHomePage script in action.
Use my PnP PowerShell script to replace the home.aspx page
Alternative methods
Change the default homepage through SharePoint
Site Owners can use the out-of-the-box make homepage action to make any page the default homepage or welcome page. This is available from the toolbar in the site pages library. But this keeps the page name and means the default page is /sitepages/randompagename.aspx instead of the standard /sitepages/home.aspx that all sites have. From my perspective this is not great. Certainly, intranet-like sites should follow some basic content management principles. Call in a touch on the OCD side but consistently having a standard homepage is one of these for me.
Screenshot of setting a new homepage in the site pages library.
Change the welcome page site property through Site Settings or PowerShell
Previously you could use the classic settings page (typically exposed by the publishing feature) or by browsing to /_layouts/15/AreaWelcomePage.aspx to make changes to the welcome page. This method no longer works and throws an error.
As with the make homepage action describe earlier this changes the default homepage to the use the page name you have provided and means the site won’t be available if users have bookmarked the site with the page name (/sitepages/home.aspx) in the URL.
Screenshot of the welcome page site settings page.
What is my point? To this day can I still memory recall core settings pages. With these, you can quickly review or makes changes to settings pages rather than using the UI to navigate to them. This includes those that may no longer be exposed in the UI. Whilst my memory serves me well I don’t recommend this approach as these pages and settings are gradually being replaced with alternatives or removed by the SharePoint and Office 365 engineering team for a reason.
Instead, you can also use Pnp PowerShell to change the site welcome page property. I’ve provided an example script below.
As simple as my script is, it is the approach worth learning the most. I hope you find this article useful and as with all Pnp development effort. Sharing is caring!
You can download Microsoft Edge based on the Chromium engine from the Microsoft Edge Insider website. Keep an eye out for all the great stuff that is coming soon such as Internet Explorer mode, a Privacy Dashboard and much more.
What do we call the new version? Microsoft Edge. But for those having technical conversations or writing any guidance or documentation the difference will need to have a term to refer to the two very different versions. On Microsoft Docs, the documentation seems to refer to the original version as Edge (EdgeHTML) and the new version Edge (Chromium).
Oh, and with Edge (Chromium) not only am I now able to manage my bookmarks in more than a frustratingly annoying pop-out pane, but I can also consolidate them between the various browsers I have used!
Microsoft Demos
Here at Microsoft, we use the Microsoft Demo Program to provision demo Office 365 environments. This service is available to Microsoft employees and Microsoft Partners.
Both can create up to six 90-day tenants, and Microsoft employees can create three additional 1-year tenants. The 90-day tenants sometimes expire sooner than 90-days, this is because they are pre-provisioned and sit in stockpiles ready for use for up to 45 days before the tenant is deleted and the stockpiles are automatically refreshed. Two types of virtual machines can be created. A standalone VM which isn’t associated with a tenant and a tenant-joined VM which gets domain-joined to a specified tenant. I don’t tend to find myself using VMs by Microsoft Demos as I tend to do this myself in my Azure subscription.
My environments are all numbered and match my Edge profiles.
Tips on managing your Microsoft Demo environments
Firstly and most importantly I know it seems a hassle but demonstrate your environment with MFA enabled. It’s a piece of cake to enable MFA. We are and should already use it for our sign-ins, so in real terms, nothing is lost by enabling it and your environment is immediately securer as a result. Security absolutely should be at the forefront of any demonstration alongside our kick-ass product and feature stack.
Tip: You can set a personal PIN in your account profile when signed-in to Microsoft Demos. This is used in combination with another string to form a password.
Add reminders into your calendar a few weeks ahead of the expiry of your environment. This gives you a chance to escalate a renewal or allow you to tear down anything you have been working on that you might want to save and avoids unnecessary stress when you realise you need an expir(ing/ed) environment!
Bookmarks
In each of my browser profiles, I include a standard set of Office 365 links. These are mainly to speed up my workflow, but it’s great to see all the shiny Office 365 icons on the bookmark bar too! Additionally, I also use folders with links to anything I am building or working on so I can quickly load them all as tabs (right click on the folder > open all on the folder). I toggle the visibility of the bookmark bar when presenting to customers and creating screenshots.
Useful bookmarks added to the bookmarks bar in Edge.
Browser settings
I tend to make all my profiles use the same configuration mainly for consistency, but some also increase productivity.
Home button – always enable the home button to speed up browsing.
I always add the English (United Kingdom) language for localised spelling.
Always show the bookmark bar (can quickly toggle it with Ctrl + B when taking screenshots or presenting to customers as needed).
Set the browser to continue where you left off on start-up.
Extensions
In the non-chromium version of Edge (EdgeHTML) I was dependant on a few browser extensions which up until last week were prohibiting me from solely using Edge (Chromium) as they weren’t available. You can now allow extensions from other stores which has allowed me to install them and to ditch my other browsers altogether.
Grammarly – I know where my weaknesses are and have invested in Grammarly premium for a number a year or so. Grammarly helps me understand the mistakes in my writing and helps improve my spelling and grammar throughout my day.
1Password * – my password manager tool of choice.
AdBlock – blocks ads from all over the web.
Save to Pocket – useful for saving research for reading later. I use Pocket to my read it later tool of choice. I often read from my Pocket list when travelling and have time set aside each week to get on top of my reading list.
OneNote web clipper * similar to above but rather than reading the article later I clip it to my OneNote notebook for reference.
Readme file
Here is my little bonus tip! I add a secret markdown readme file hosted in Gist provided by GitHub for each of my environments. The primary use for this is to provide a summary of the environment, the key personas like the admin account (note I don’t store passwords in this file) and to provide a basic changelog as you can easily forget significant changes in these environments that then catch you out later.
I decided to use a secret Gist rather than a OneNote page as the readme file is only ever used for read-access. Therefore, a secret Gist URL is just perfect for this and quick too! I also add this to the bookmark bar, so I quickly know what environment and profile I’m using. I then pin this tab, so it is always discretely open for quickly referencing.
Example readme markdown file hosted as a secret Gist in Git Hub.
Other useful tools for demos
Here are some other tools I use alongside these labs to help me with my task and demonstrations.
Clipboard manager – ClipX is a lightweight tool which I’ve used for years but now opt for Phrase Express for its additional Macro functionality.
Collection of sample files – basic folder comprising of sample files and Office documents. I also have a piece of sample malware file (EICAR test file) useful for demonstrating security capabilities in Office 365 such as Exchange Online Protection (EOP).
ZoomIT – a really useful tool to magnify parts of the screen when presenting but also useful for time management if you have an exercise or break.
Multiple desktops in Windows 10 – they’re great for keeping related apps and content together, for focus and for demonstrations where you can have various personas in each desktop and use a multi-finger swipe on the trackpad to slide between each desktop.
FastStone Capture – my screenshot tool of choice, it has advanced capture capabilities such as an object within a window such as a toolbar and can capture a long page with scrolling capture. It also has a simple yet powerful editor and can blur sections and add incremental annotations.
AirServer – this is an excellent tool for mirroring the display of mobile devices on your Windows desktop. The tool supports mirroring devices that use Airplay, Miracast and Google Cast.
One thing that doesn’t appear to be possible is that you can’t create a shortcut directly to a given profile. When launching Edge from a shortcut it will use the last profile Edge used. I’d rather it open a specific profile such as my default personal profile rather than the mythical demo personas I mostly use profiles for.
I hope you find the tips and tricks in this article useful.
A challenge for most administrators managing more than one or more Azure subscriptions or Office 365 tenants having to continuously log in and out with different credentials to do so.
Login error in Office 365
Many have developed techniques to work around this challenge by using Incognito Windows or Private Browsing and others use multiple Browsers. Even with these methods, you are still limited to using two accounts particularly with Incognito Window or Private Browsing technique.
In this post, I share my method that enables you to log in to multiple Office 365 & Azure accounts in the same browser, on the same device at the same time!
Here’s an example of how many accounts I toggle between:
Microsoft Account for Corporate used for Azure Management Portal, Intune, Visual Studio Online and MSDN
Personal Office 365 account
Multiple Customer accounts (or through Delegated Administration using my Corporate Office 365 account).
Multiple Developer Office 365 accounts
Multiple Demo Office 365 accounts
Sure, a password manager might help with the login process by storing credentials but this still doesn’t solve the challenge of being signed in to multiple accounts at the same time.
The technique I have started using is a feature available in Chrome. Chrome allows you to create multiple user accounts from the Settings page.
Users in Chrome Settings
I’ve created users for each of the Microsoft accounts I commonly use. Each Chrome user has its own settings such as the plugins installed, the bookmarks that are available, browsing history and the crucial part cookies and Browser sessions.
Now when I want to jump between Azure subscriptions or Office 365 tenants I can toggle between Chrome users. The user menu is available in a number of places.
Chrome Users is also available on the PC version of Chrome. I hope you find this technique of switching between Azure or Office 365 accounts useful.
I have just discovered that you can give feedback about your experiences using Office 365 directly to Microsoft using their online feedback form (http://msft.it/o365feedback) thanks to a Tweet from Jennifer Mason.
As someone who has multiple @Office365 logins I find it impossible to be able to switch as quickly as needed between them :(
It is a great tip for those working with Office 365, SharePoint Online and Yammer etc who want to pass on feedback to Microsoft about their experiences using Office 365.
This post is part of SP14 Keynote highlights series where I provide some highlights of the next version of SharePoint. These highlights are from the SP24 Conference Keynote that Bill Baer delivered.
SharePoint Site Folders
How many occasions have you tried to access a document in SharePoint, but end up having to click through a long set of links to find it because you can’t remember the URL? OK, this is not an everyday issue, but we do use SharePoint to store documents and we use SharePoint sites to create contextual containers to store documents in. In someways, these SharePoint sites slow us down from accessing documents harder.
In the next version of SharePoint (SharePoint 2016) we might find a new method to access Document Libraries called Site Folders. Site Folders will provide a list of all Sites that we have access to that contain Document Libraries (a.k.a Site Folders or Site Libraries) and will be available from OneDrive for Business.
Site Folders coming to SharePoint 2016.
Users will be able to click-through into individual Sites from the Site Folders page to easily discover Document Libraries each site contains.
Libraries visible through the new Site Folders area coming to SharePoint 2016.
I wonder how this will impact how with architect document management solutions. Search is becoming more and more powerful than we are shifting to an era where Information Architecture and Taxonomies become less relevant (or maybe more relevant behind the scenes), time will tell!
I have an idea what Microsoft is trying to do here, watch this space as I’ll provide my own mock-up with an example soon.
Discover more
Join me over the next year as I discover more news and information about the next version of SharePoint and Office 16 by following my #Office16 tag.
This post is part of SP14 Keynote highlights series where I provide some highlights of the next version of SharePoint. These highlights are from the SP24 Conference Keynote that Bill Baer delivered.
OneDrive for Business to change the way we distribute and store Outlook attachments
We all do this. We need to send a file to someone via email and we just attach the file to the email and press send.
60% of mailbox storage is allocated to attachments.
What we should all be doing, of course, is saving the attachment to SharePoint and including a link to the attachment instead. Microsoft may be about to make this much easier in the next version of SharePoint and Office (SharePoint 2016 and Office16) by slipstreaming the entire process and integrating Outlook with OneDrive for Business in Office 365.
Send a link or attach a copy – integrating Outlook with OneDrive for Business
Attachments will be stored in a “Attachments” folder in the user’s personal library in SharePoint Online, known as OneDrive for Business.
Attachments folder in the next version of SharePoint – SharePoint 2016.
Each attachment will be secured to those on the recipient list of the originating email.
Outlook attachment store in OneDrive for Business.
Benefits of storing attachments in OneDrive for Business include reducing overall email storage requirement but what do users care…general they don’t, not about storage requirements anyway. But what about providing themselves and their recipients with the ability to collaborate on attachments centrally and even use Co-Authoring. Imagine how much email traffic will be reduced because everyone has access to the same attachment.
Outlook attachments stored centrally in OneDrive for Business.
There are times when storing attachments centrally SharePoint 2016 or whatever it becomes will be useful but not in all examples. Most of us are fortunate to live in a very connected world but there are times when we’re not so connected. This exciting change would mean at the time an email attachment would not be accessible, even though the original email is available on mobile for example. I look forward to hearing what others think about this new feature.
Discover more
Join me over the next year as I discover more news and information about the next version of SharePoint and Office 16 by following my #Office16 tag.
This post is part of SP14 Keynote highlights series where I provide some highlights of the next version of SharePoint. These highlights are from the SP24 Conference Keynote that Bill Baer delivered.
Updated Command Surface in SharePoint Online
The Command Surface that is available at the top of List and Library pages is being updated in SharePoint Online over the coming weeks. A message about this change has been available in the Office 365 Message Centre (MC4558) for some weeks now.
Command surface coming to SharePoint Online.
The change is intended to simplify access to common commands. The commands are now enlarged, include icons and there are additional commands to sync, edit, manage and share documents.
Close-up of the new command surface coming to SharePoint Online.
While this is not a new feature to SharePoint, it does demonstrate the continuous investment and development that is happening in Office 365 and SharePoint Online. Better still it is a further example that Microsoft is listening to customers – in this example, how commands were not easily accessible and hidden in the ellipsis menu.
Discover more
Join me over the next year as I discover more news and information about the next version of SharePoint and Office 16 by following my #Office16 tag.
This post is the first of my SP14 Keynote highlights series where I provide some highlights of the next version of SharePoint. These highlights are from the SP24 Conference Keynote that Bill Baer delivered.
“Shared with Me” coming to SharePoint
Something to look out for in the next version of SharePoint (possibly SharePoint 2016 or Office16) or even soon is a summary of documents and folders that have been “Shared with Me”. It appears that the “Share with Me” page is already available in SharePoint Online, however, the summary of folders shared with you isn’t.
Folders Shared with me summary in the next version of SharePoint.
It’s pretty self-explanatory but a list of documents or folders that have been shared with you will be displayed in your OneDrive for Business site.
List of items Shared with me in the next version of SharePoint.
I wonder if this might extend to include scenarios such as multiple environments or Office 365 sites, to create a true consolidated view of files that have been shared with you. I’m always searching my inbox to find emails from colleagues where they have shared files with me in one single place for this information would be well received.
Discover more
Join me over the next year as I discover more news and information about the next version of SharePoint and Office 16 by following my #Office16 tag.
In this post, I share information about On-Premises SharePoint, highlights of SharePoint 2016 and see how Outlook attachments (bye-bye) are changing as we know them.
Firstly I’d like to congratulate the SP24 Conference (#SP24Conf) organisers for delivering an awesome conference this week. The format was new and a challenge for those involved I’m sure. It worked very well aside from the twenty-first-century hiccup or two. I look forward to the next one when the crew have all recovered and caught up on their sleep. Maybe I might be able to get a speaker slot next time where we might hear more about SharePoint 2016!
I managed to stay up for three sessions before calling it a night (a late one at that – 2 am UK time. I was delivering an Azure briefing at the Microsoft Offices in London the next morning. But I did manage to attend five other sessions towards the end of the day. Hopefully, in a few weeks, we will have access to all the sessions when I’ll try to watch as many sessions as I can when the time arises.
SharePoint 24 Conference – Keynote delivers important industry news and SharePoint 2016 highlights.
SharePoint 2016 highlights and more…
I’d like to share some highlights I learned during the SP24 Keynote that Bill Baer’s delivered. It’s important news for all those involved in the industry to hear at this time. More importantly, it demonstrates again that Microsoft is continuing to share more and more with us long before they would have done before.
SP24 Keynote available on YouTube
SharePoint On-Premises lives on
With Microsoft investing so much in their Cloud products whether that’s Office 365 or Microsoft Azure, many have thought that time had been called for the On-Premises version of SharePoint. Well, that time is not in sight – not yet anyway!
So the next version of SharePoint that we’re shipping in later 2015 will in fact not be the last version of SharePoint server that we ever ship.
Sure we’ll see features and changes to these Cloud products more often especially Office 365, long before we see them On-Premises. We might not see some features at all but Bill said, “Microsoft will continue to develop in On-Premises for as long as there is demand for it”. SharePoint 2016 is not going to be the last.
We are going to continue to ship SharePoint server on-premises as long as there is a demand for SharePoint server on-premises!
Not only that but SharePoint 2016 will ship towards the end of 2015.
In late 2015 we are going to launch another version of SharePoint server to our on-premises audience.
SharePoint 2016 highlights
On top of the On-Premises news, Bill also demonstrated features from the next version of SharePoint – SharePoint 2016. Here are some highlights from the Keynote:
The close integration with Yammer was clear once again and more Office Graph functionality seemed to be visible since the demonstration during the SharePoint Conference 2014 (#SPC14).
We also learned about Remote Index. This will make it possible to push On-Premises Search Indexes to Office 365 to provide a single search experience and result set. A unified search index in Office 365 along with Office Graph will create an awesome experience for end-users.
Outlook is the first program that many of us launch on a typical working day yet we have many other sources of information. Expect to see changes to Outlook that will help us access this information and deliver more than just email to us.
A further change to Outlook and SharePoint 2016 that we’ll see in the next version is the removal of email attachments as we know them with the help of OneDrive for Business. Users will continue to attach files to their emails but they’ll be saved to their OneDrive for Business Document Library and shared with all to, cc and bcc addresses via a URL in the email. This is a really exciting change and I look forward to discovering more about soon. The net result is users will have continuous access to the latest files and can use features such as Co-Authoring.
Discover more
Join me over the next year as I discover more news and information about the next version of SharePoint and Office 16 by following my #Office16 tag.
It’s official you can now customise the Office 365 login page with your own branding – ok not quite yet but Microsoft has just released a preview feature that will soon allow us to.
The dull Californian highway image that we are all accustom to can now be replaced with your own image along with your own logo and login information which is impressive in itself but these elements can also be localised for different languages. This is all achieved with a preview feature Microsoft have recently released for Windows Azure Active Directory Premium which of course underpins Office 365. Pricing for this feature is not yet available but I imagine it will be published soon.
Example of a customised login page
What can be customised?
Microsoft has made the following elements of the login page customisable.
The “Banner Logo” which is displayed on the sign-in page and access panel.
The “Sign In Page Illustration” displayed on the sign in page to the left of the login form.
The “Sign In Page background colour” visible when there is no sign in page illustration present or for low bandwidth connections.
The “Sign In Page Text” that appears below the login form and can be used to give more information to users such as where to get support.
The “Tile Logo” which is not used but might be used to replace the “organisational account” pictogram.
A “User ID Label” which again is not used but could be set to “Company email” or “User ID”.
Browse to the Active Directory page and select your Office 365 directory.
Click on the “Enable Active Directory Premium” link on the summary page.
Then from the summary page click on the “Customise your organisation’s Sign In and Access Panel pages” link where you will be able to upload your logo and other assets.
Customise branding form
As this is a preview feature Microsoft has decided for the first few weeks of the preview that users must opt-in on each device to experience the customised sign-in page. To opt-in, you must visit https://login.microsoftonline.com/optin.srf.
Demo customised sign-in pages
Microsoft has also provided to demo fictitious sign-in pages that you can get access to experience a customised login page.
The default interval for Windows Azure Active Directory Sync (DirSync) synchronisations is 3 hours. If for instance, your Active Directory has lots of changes you probably want to consider shortening the sync interval.
The schedule can be modified by changing the “Microsoft.Online.DirSync.Scheduler.exe.Config” configuration file. Before proceeding to make any changes to the sync interval you should evaluate how long it takes to complete synchronisation. You can do this by reviewing the application event log for entries that indicate when sync has started and completed.
To modify the configuration file open “C:\Program Files\Windows Azure Active Directory Sync\Microsoft.Online.DirSync.Scheduler.exe.Config” in Notepad. You will then need to modify the value of the “Synctimeinterval” key – the notation of this is Hours:Minutes:Seconds.
Microsoft.Online.DirSync.Scheduler.exe.Config
Save the configuration file and restart the “Windows Azure Active Directory Sync Service” Windows Service (via PowerShell Restart-Service MSOnlineSyncScheduler) to apply this change.
When configuring Windows Azure Active Directory Sync (or DirSync as it was previously known) it’s useful to be able to run various synchronisation tests. The default synchronisation schedule is 3 hours so unless you want to wait you will need to force a full synchronisation using PowerShell.
Start-OnlineCoexistenceSync cmdlet
To do this you need to load the Windows Azure Active Directory Sync PowerShell module and run a cmdlet. Start by navigating to “C:\Program Files\Windows Azure Active Directory Sync” in PowerShell and then run “.\DirSyncConfigShell.psc1” from this directory. This will launch a new PowerShell console with the Windows Azure Active Directory Sync PowerShell module loaded (Add-PSSnapin Coexistence-Configuration). Then to force a full synchronisation you need to run the Start-OnlineCoexistenceSync cmdlet.
You can verify that synchronisation has occurred by reviewing the application event log on the server running DirSync – there should be several items in the log such as “Directory Synchronization, Event ID – 114, Export cycle completed”. There is also a status of the Active Directory Synchronisation on the “Users and Groups” page in the Office 365 admin portal. There are also two other ways to see the status of synchronisation jobs which I will go into in more detail in a later post but these include using the Forefront Identity Manager (FIM) client and Fiddler web debugging proxy.
Office 365 Active Directory Sync status
You can create a shortcut to “C:\Program Files\Windows Azure Active Directory Sync\DirSyncConfigShell.psc1” on the desktop for ease of administration. I, however, take this one step further and create a shortcut to perform a synchronisation as well. Create a shortcut with the following target below.
