Slide deck from the San Diego Office365 Saturday for "Top 5 Tools for SharePoint Newbies." Geared towards users who find themselves suddenly in charge of SharePoint, but without the tools to get the job done right.
5. End User
becoming a Citizen
Developer
Traditional IT Pro
inheriting
SharePoint after the
consultants left
Project Manager
using SharePoint
Document Sets
Can you Relate?
6. THE TOOLS
• SharePoint Admin Center
• SharePoint Management
Shell
• Visual Studio Code
• Power Automate
• SharePoint App Catalog
7. SHAREPOI
NT ADMIN
CENTER
• Search and filter all sites
• Change site URLs
• Register Hub Sites
• Site Creation Options
• “More Features”
8. HOW DO I
GET IT?
Must be a Global (Tenant) or SharePoint
Administrator
Access from the waffle menu
/_layouts/15/online/AdminHome.aspx#/home
9. SHAREPOINT
MANAGEME
NT SHELL
• Task Automation and Configuration
Management
• Download Management Shell
• Cmdlets are building blocks:
• Get-SPOSite
• Add-SPOSiteDesign
• Invoke-SPOSiteSwap
• References and Documentation
Online
10. HOW DO I
GET IT?
• Download for free from the Microsoft
Download Center!
https://www.microsoft.com/en-
us/download/details.aspx?id=35588
11. POWER AUTOMATE
For Developers…
• Easy intro to development
concepts in a graphic
interface
• Connect to different data
sources
• Quickly automate business
processes
For Administrators…
• Power Platform admin center
• Automate PowerShell tasks
(Advanced)
12. HOW DO I
GET IT?
Seeded through your existing
Office365 license
Access from the waffle menu
flow.microsoft.com/
13. VISUAL
STUDIO
CODE
• Tool for writing and
maintaining code
• JSON, PowerShell
• Javascript, HTML
• Intellisense
• Beautify Code
14. HOW DO I
GET IT?
• Download for free!
• https://code.visualstudio.com/download
15. SHAREPOI
NT APP
CATALOG
• SPFx App Packages
• See what has been deployed to
your environment
• Providing access
• Assisting in custom code
deployment and installation
16. HOW DO I
GET IT?
Must be provisioned
May already exist in
tenant
17. BONUS TOOLS!
• Microsoft Graph Explorer https://developer.microsoft.com/en-
us/graph/graph-explorer
• Azure https://portal.azure.com/
• Community Forums https://powerusers.microsoft.com/
• All Admin Centers
https://admin.microsoft.com/AdminPortal/Home#/alladmincenters
18. EVENT SPONSORED BY
MARTHA CASTIGLIA IN
LOVING MEMORY OF TOM
4282 Esplanade
Court,
San Diego, CA 92122
The end user who copied and pasted some stuff called JSON from the Microsoft Documentation and who is now the “SharePoint Developer” for the company
The traditional IT pro who inherited SharePoint after the consultants left and really doesn’t know where to start
The Project Manager who figured out how to use Document Sets in a SharePoint library to manage project files and is now in charge of SharePoint Administration and maybe sort of process automation
Ideas for presenting the personas: the “before” as they see themselves, and the “after” as they are now EMPOWERED!
If you find yourself relating to one of these personas, here are some questions you might be asking yourself:
Why am I in IT?
Am I still a PM?
All I did was copy and paste some JSON stuff from the documentation. I’m not a developer, right?
You! You’re my citizen developer!
PACE: no later than the 10 minute mark when this is finished
1 minute
5 Mins
Of course, we have to kick it off with the SharePoint admin center. This is your one-stop shop to get an overview of all the SharePoint sites in your tenant, and there have been so many recent additions to functionality, things that you used to have to do in PowerShell but that you can now handle with just a few clicks.
Admins and Devs alike will visit the admin center often.
I suggest getting in here and poking around– familiarize yourself with what you can do, such as Policies and Settings
Search for sites, filter by owner, filter by hub name
Common Requests:
Change URLs and site names
Register and unregister sites as hubs
Manage External sharing settings
Manage Site Creation options
Turn on or off subsite creation option
Turn on or off the “Comments” section on site pages
Familiar with Central Administration from On-prem? Look under “More features” for things like Term store, User profiles, and Search settings.
PACING: 15 minute mark
8 Mins
If you’re NOT familiar with what this is, PowerShell is a scripting language that helps with task automation and configuration management. That’s a mouthful, but when you think about it, that’s exactly what you want. With SharePoint you’re going to run into plenty of situations where you need to repeat tasks over and over again, such as adding users to sites, performing site or permissions audits, or bringing legacy information into SharePoint from outside sources such as Excel, SQL, etc.
In order to get started with PowerShell for SharePoint you’ll want to download a SharePoint-specific PowerShell console called “Management Shell.” This is basically just a tool that comes preloaded with all the “cmdlets” you’ll need to talk to SharePoint Online.
Everything we do in PowerShell starts with what are called “cmdlets.” These are the building blocks of PowerShell scripts, and each one refers to specific functionality and may take various parameters. You’ll often see them structured as “Verb-Noun”
Examples are:
Get-SPOSite
Add-SPOSiteDesign
Invoke-SPOSiteSwap
If asked, mention that PnP PowerShell runs from within the default PowerShell console, NOT management shell
DEMO: Connect-SPO –URL site url; get-sposite
PACING: 23-25 minute mark
8 Mins
Power Automate is a great place to start automating tasks once you’re familiar with how your users are working with SharePoint.
This is really a split “top tool,” as developers and admins can both use Power Automate, but admins may be less interested in the functionality and more interested in the admin center
Mention name change from Microsoft Flow to Microsoft Power Automate…but we still create “flows.”
To access Power Automate: Just be a licensed user in your tenant
To access the Power Platform Admin center: Either be a Global (tenant) admin, or be assigned the Power Platform Admin role by a global admin.
Devs:
Easy introduction to development concepts such as variables, loops, filters, APIs, etc. in a graphic interface
At intermediate level, transition to things like using PowerShell with Power Automate
At advanced level, take what you’ve learned about apply those same concepts to learning SharePoint framework
Admins:
Tool to help automate common PowerShell tasks (using azure automation)
Review the Admin center in Power Automate to understand who has access to what and who is creating apps and flows in which environments
DEMO: Create from within SharePoint, for a specific item
PACING: 31-33 minute mark
3-5 mins
Both admins and devs find Visual Studio code useful for the same reason: intellisense and support for multiple programming languages.
Devs:
Even if you’re a complete newbie, you’ll quickly find yourself writing light JSON and PowerShell, and for sure as you progress as a developer you’ll add in things like JavaScript and HTML in order to support SPFx web parts.
Admins:
As a new administrator, Visual Studio Code goes hand in hand with using SharePoint Management Shell. You can write and test your powershell right from within VS Code as you begin to progress to handle more complex administrative tasks via PowerShell.
Tips:
Beautify your code
Easy to read
Use it to edit your JSON
For SharePoint column and view formatting
For JSON in Power Automate: inspecting and adjusting
DEMO: JSON body from Power Automate; beautify PowerShell cmdlets
PACING: 35-38 minute mark
3-5 mins
I include this here not because I think you’ll immediately be uploading applications here, but because you need to know what is it and how it works.
Admins:
You care about this because you need to know who is uploading applications to your tenant and where they are deployed. You are the curators and caretakers, and it’s worth working hand in hand with developers on your team to understand what is happening where. If your developers are not ALSO admins, you’ll be the ones providing access to this and you may also be asked to upload packages and deploy them. It’s best to have some knowledge before that situation arises.
Devs:
You care because this is where you’ll live if you’re creating custom SPFx web parts and extensions!
Gotchyas: some issues with the modern interface and uploading from there; just use the classic
PACING: 38-42 minute mark
It may already exist in your tenant, especially if you’re inheriting a tenant that is already being used and that already has custom web parts deployed.
The url will depend on what was specified, because it really is just a site. It’s usually /catalog or /appcatalog,
DEMO: Show how to provision it and how to see whether or not it’s already provisioned
3 minutes (43-45 minute mark, with time for questions)
Tools that didn’t make my “top 5 newbie list” for whatever reason– either too “advanced” to be newbie, or not specifically relevant to both admins and devs
PACING: only review these if time permits; this is a filler slide