I had the honor of co-writing Packt’s new MS-700 exam guide with fellow MVP and MCT Peter Rising. We cover the latest exam objectives released in over 400 pages that include plenty of screenshots and a total of 165 exam practice questions.
Successfully passing the MS-700 exam earns you the Microsoft 365 Certified: Teams Administrator Associate certification. This is an excellent way to prove skills and proficiency to employers (current and prospective) and also challenge yourself with keeping up-to-date on administering one of Microsoft 365’s core collaboration and communication apps.
I also want to thank the many editors and staff at Packt who invited us to work on this project and helped us make it exceptional from beginning to end. It’s our success to celebrate together and I’m quite proud of what we’ve accomplished.
This announcement shared that “Microsoft Teams meeting organizers will be soon be able to create a custom registration page for any meeting, although the feature is designed for webinars.”
When can I create custom registration pages for Teams meetings and webinars?
The feature will apply to both desktop and web versions of Teams and may be seen rolling out to your tenants as early as March and as late as April.
What Teams meeting types can have custom registration pages?
Webinars are the ideal candidate for this feature but any normal Teams meeting will work. Recurring meetings and channel meetings, however, will not have this ability.
Who can create custom registration pages in Teams?
Anyone in your tenant will be able to create custom registration pages for their meetings by default.
Who can submit/complete custom registrations for my Teams meeting?
Your organization’s users are able to submit by default, but you can change this everyone (public) to host public webinars. Your admin will need to grant you the ability to create public registration forms, and once granted you can use it repeatedly until access is revoked.
You create a custom registration form during the normal meeting scheduling process. Anyone you invite to the webinar/meeting will automatically receive the link to your form for registration. Others can use your link from social media posts, emails, blogs, etc.
Meeting organizers will have access to a downloadable registration report to track registration activity. This can be found on the “details” tab for the meeting at any time.
The wiki tab that is added to every Team and each of its channels is convenient, but not robust and its content is not easily migrated and shared. I typically recommend new Team owners (or admins setting up new Teams) delete the ‘Wiki’ tab that comes with the Team and insert a new OneNote tab called ‘Notebook.’
Why replace the wiki with OneNote?
OneNote has a dedicated app.
Notebooks and Wikis are both stored in SharePoint (not Teams)
Notebooks can be moved, migrated, archived and accessed later more easily as a standalone OneNote file.
Wikis are folder structure document libraries in your site’s Site Contents folders. Individual sections are saved as .mht files. This can get messy reassembling and manipulating.
OneNote is easily searchable and can have password protected areas. Try searching your wiki or restricting certain parts without creating a private channel.
OneNote supports drawing/writing with styluses (styli?)
OneNote supports audio/video
OneNote integrates with Outlook
There are more reasons, like how robust you can get with formatting text, but I think you get the picture.
Why you might keep the wiki
While I’m suggesting that OneNote be used for your Team’s note-taking, collaboration, and regular information sharing in a highly mobile and flexible medium, there is still a case to keep wiki alongside OneNote. Matt Wade suggests renaming the wiki tab to ‘About’ and using it as a reference/resource for the Team itself in his Definitive Guide to Everyday Etiquette in Microsoft Teams. So then you’ll have a simple ‘About’ tab for Team information and a ‘Notebook’ tab for ongoing collaboration and work.
How to replace wiki with OneNote
Use the dropdown menu for the Wiki tab and select Remove
Click the plus sign (+) to add a new tab and select OneNote for the tab.
Select the Notebook, and if for a channel other than general, perhaps a corresponding section in the Notebook. (I recommend mirroring your notebook’s sections to your Team’s channel structure)
Use the tab dropdown menu to rename the probably-very-long name to something simple like ‘Notebook’ for a cleaner user experience.
That’s it! Just a few steps and you’ve substantially increased the productivity potential and collaboration superpowers of your Team. You’ll want to repeat these steps for each new channel you create and, as mentioned, consider creating a new notebook section for each channel to keep things simple, organized, and easy to navigate.
Still aren’t convinced?
Bob Morris has done a very impressive and thorough job of comparing the two. His thoughts on the matter may help you decide whether wikis or notebooks are the best fit for your Team(s).
Shifts, formerly StaffHub, is an app available for use within Microsoft Teams to share schedules and allow employees to submit requests. There is also a mobile app that can be used for many of the same desktop features, and adds a clock in/out functionality for members.
In this post, I’ll go over some Shifts basics to give you an idea of what’s possible. Please note you must be a Team owner to set up Shifts for your team.
Set up Shifts for the first time
To get started using Shifts, open Teams and select the ellipses from the left menu. Here you can select the Shifts app.
Next, you’ll choose the Team for which you’re configuring Shifts. Click Create next to the correct Team.
Next, confirm the time zone you want to use for this team. Once correct, click Confirm.
Add groups/types of shifts
Next, you’ll want to do some planning. What types of Shifts are you going to be scheduling? For each “type” of shift, you’ll create a group.
Click Add group and enter a name for each group/type of shifts or roles.
Once you’ve added all the possible types of shifts, you may wish to reorder the shift groups. Just click the “move” button on any of the groups, then drag the groups into the order you wish and save.
Add members to groups/roles
Choose who will have shifts in each group by selecting the “add people to group” icon.
Add members you wish, then close the dialog.
A person can be a member of multiple roles. For example, I may have shifts in concessions AND the admin office. You must add these members manually to each group they’ll appear in – they are not automatically added to all groups.
Add shifts for members
You can double-click in any square on the schedule to add a shift.
If you add a shift to “Open shifts” you can assign it later.
Share/publish the schedule
As you add Shifts, changes will be marked with an asterisk meaning only you as an owner can see them. You must Share with team to publish changes and let others see the schedule.
After clicking Share with team, you choose which dates to “publish” and whether to notify the entire team or just those affected by the changes/additions.
Remember to “share” every time you make changes so members are aware of your edits or new schedules.
Adding time off for members
To add time off for a team member, just right-click a square in their row and choose Add time off. Time off will appear in ALL groups for that team member – you can’t have a sick or vacation day in one shift group, and work in another.
You can classify these time off shifts in different ways, and save when satisfied.
If someone requests time off after they’ve already been scheduled you can move their affected assigned shifts to open shifts to re-assign later or have them make a request for someone to cover them.
Your team members, not just owners, can make their own requests for time off, swaps, or offers (giving a shift up without taking another in return). This takes some of the administrative burden off owners and makes employees accountable for their own changes and communication.
Time off requests
Employees can request time off, which sends a request for approval to the manager/owner.
When time off has been requested, a pulsing orange dot will appear with the request on the schedule itself, not just in the Requests tab.
Members can offer to exchange shifts with another person. The other employee must accept the proposal for it to take affect. When making the request, your employees will be able to tell which “group” the shift is in easily.
Sometimes employees just want to give a shift away without taking another in return. They can “Offer” shifts to other employees which sends the other employee a request for approval (similar to swaps).
Not all members may have easy access to Teams at all times, so you can easily print the schedule and post anywhere.
Using the “scale to one page” setting to make sure it will fit on your desired paper size.
The next logical piece, after scheduling, is the actual shift performance itself. Shifts even includes a Time Clock feature which allows mobile clock-in and clock-out with optional location detection for reporting.
If you choose to turn on location tracking, you must enter the coordinates from which you expect employees to be clocking in and out.
From the Teams mobile app, team members can then clock in and clock out. They can edit clockings before confirming (in case they forgot to clock in/out) but the export/report will note the entry was edited. When clocking in/out, members will be notified if they’re noticed as off-location but can still clock in/out with that note added to the record.
The export (Shifts > Settings > Time Clock > Export) will highlight those clock-ins and clock-outs that were off-location:
Shifts comes at no additional cost with your O365 subscription. It could easily replace your Excel sheet schedules or expensive clock in/out software. While it may not be the best solution for all scenarios, I’d argue it could be a game-changer and cost-saver for many organizations and committees or event staff.
O365 groups make up the sun in the O365 solar system. And every Microsoft Teams team (planet?) must have an O365 group to exist. You’ll also use O365 groups for group email and calendars, defining permissions for private Stream channels, collaborating with group members in Planner, and much more.
When you create a new team from scratch, it automatically creates an O365 group (and a SharePoint site collection). Whomever you invite to that team is added to the O365 group which is also used to define permissions in other apps and services throughout O365.
But let’s say you were using O365 groups before Teams was cool. You don’t want to create duplicate teams or have to manage twice as many, right? Luckily, you can use existing O365 groups to create new teams.
Create a team using an existing O365 group
In Teams, beneath your list of Teams, click Join or create a team.
Click Create team.
Choose Create from…
Next, click Office 365 group.
If you choose Team, it will copy that Team’s apps, settings, and channels to the new Team (without changing the original Team). This might be useful for classes with similar formats, or creating committees or teams based on a well-received template.
But to create a team from our existing O365 group, we’re going to select Office 365 group.
Now select the existing O365 group for which you’re establishing a new Team, then click Create.
After a moment, your new Team will be created and you’ll be taken to its landing page.
You can verify membership is correct by opening the Team’s menu (ellipses) and selecting Manage team. This
Here you can view owners, members, and guests from the O365 group. You can now modify the O365 group’s membership here if you wish, keeping in mind it affects permissions outside of Teams as well (as is the nature of O365 groups).
Microsoft recommends modifying O365 group permissions via Teams because doing so elsewhere (such as the M365 admin center) will cause a delay in taking effect and removed team members may retain Teams chat access for a couple hours.