Lab 09: Microsoft Teams Collaboration

Configured Microsoft Teams collaboration for Nietz Ltd through a private helpdesk workspace and a separate organisation-wide announcements team, validating membership, channel posts and shared files.

Overview

In this lab, I extended the Microsoft 365 environment into Microsoft Teams collaboration. I used the existing Nietz Ltd users and created a private IT Helpdesk Team for restricted support collaboration.

I also created a separate Company Announcements Team as an org-wide communication workspace. This kept the support collaboration model separate from broad company updates.

This lab focuses on Teams as the user-facing collaboration layer. The deeper SharePoint and OneDrive file collaboration work is handled in the next lab.

Objective

The objective was to create a controlled Teams workspace, configure owners and members, validate a standard support channel, confirm file collaboration through the Shared area, and prove access from standard user accounts.

Environment

Environment
Component	Value
Company	Nietz Ltd
On-premises AD domain	corp.nietz.co.uk
Microsoft 365 / tenant domain	nietz.co.uk
Daily administrator	[email protected]
Primary Team	IT Helpdesk
Primary Team privacy	Private
Primary Team owner	[email protected]
Primary Team members	[email protected], [email protected]
Support channel	Tickets
Member validation user	[email protected]
Org-wide Team	Company Announcements
Org-wide validation user	[email protected]
Previous lab dependency	Lab 08: External Mail Flow and DNS Records
Next lab dependency	Lab 10: SharePoint and OneDrive File Collaboration

Configuration

1. Private Helpdesk Team Created

I created the IT Helpdesk Team as a private workspace for helpdesk collaboration.

IT Helpdesk Team created in the Microsoft Teams admin center — Figure 1IT Helpdesk Team created as an active private Team.

Context: A private Team is suitable for helpdesk collaboration because access is controlled through Team membership rather than being open to the whole organisation.

2. Team Privacy and Settings Confirmed

I reviewed the Team settings and confirmed that the IT Helpdesk workspace was configured as a private Team.

IT Helpdesk Team settings showing private Team configuration — Figure 2IT Helpdesk privacy and member permissions confirmed.

Context: Settings validation confirms that the Team was not just created, but configured as a controlled workspace with private membership.

3. Team Owners and Members Configured

I configured Kristian Nietzold as the Team owner and added Chloe Bennett and Lee Johnson as members.

IT Helpdesk Team showing Chloe Bennett and Lee Johnson as members and Kristian Nietzold as owner — Figure 3Owner and member access configured for the IT Helpdesk Team.

Context: Teams access is membership-based, so owner and member validation proves that the correct users were granted access to the private workspace.

4. Standard Tickets Channel Created

I created a standard Tickets channel inside the IT Helpdesk Team for ticket discussion and support updates.

IT Helpdesk Team showing the Tickets standard channel — Figure 4Tickets standard channel created inside IT Helpdesk.

Context: Channels organise Team conversations and provide a clear location for support-specific collaboration.

5. Channel Post Created

I posted a Lab 09 validation message in the Tickets channel to confirm that the channel was usable for helpdesk conversation.

Lab 09 validation post created in the IT Helpdesk Tickets channel — Figure 5Validation post created in the Tickets channel.

Context: A channel post validates the user-facing Teams experience instead of only proving the admin-side configuration.

6. Test File Uploaded to Shared Area

I uploaded Lab09-Teams-Test-File.docx to the Tickets channel Shared area to validate Teams file collaboration.

Lab09 Teams test file uploaded to the IT Helpdesk Tickets Shared area — Figure 6Test file uploaded to the Tickets channel Shared area.

Context: Teams channel files are backed by SharePoint, but this screenshot focuses on the Teams user experience. Detailed SharePoint and OneDrive validation is handled in the next lab.

7. Member User Team Access Validated

I signed in as Chloe Bennett and confirmed that a standard member could access the private IT Helpdesk Team and the Tickets channel.

Chloe Bennett accessing the IT Helpdesk Tickets channel in Microsoft Teams — Figure 7Member user access to the private IT Helpdesk Team validated.

Context: Member-side validation proves that the access configuration worked from the perspective of a normal licensed user.

8. Member User File Access Validated

I confirmed that Chloe Bennett could access the uploaded test file from the Tickets channel Shared area.

Chloe Bennett accessing the uploaded Lab09 Teams test file in the Tickets channel Shared area — Figure 8Member user file access validated from the Teams Shared area.

Context: File access validation links Team membership to practical collaboration, showing that the member can reach shared content, not just see the Team name.

9. Org-Wide Announcements Team Validated

I created the Company Announcements Team as an org-wide communication workspace and validated access as Emily Wilson.

Emily Wilson accessing the Company Announcements org-wide Team in Microsoft Teams — Figure 9Company Announcements org-wide Team validated with a standard user.

Context: This provides a second Teams model: IT Helpdesk for restricted support collaboration and Company Announcements for broad company-wide communication.

Validation

The lab was validated when the private IT Helpdesk Team existed, privacy was confirmed, ownership and membership were assigned, the Tickets channel was available, a channel post was created, a test file was uploaded, and Chloe Bennett could access both the channel and shared file.

The supporting org-wide validation was completed when Emily Wilson could access the Company Announcements Team and view the announcement post.

Key Technical Outcomes

This lab demonstrated how Teams workspaces are controlled through privacy, ownership, membership, channels, posts and user-side validation.

It also showed the difference between a restricted private Team for support collaboration and an org-wide Team for broad internal communication.

Summary

I created the private IT Helpdesk Team for restricted helpdesk collaboration.
I configured Kristian Nietzold as owner and added Chloe Bennett and Lee Johnson as members.
I created the Tickets standard channel for support discussion.
I validated channel posting and uploaded a test file to the channel Shared area.
I confirmed that Chloe Bennett could access the Team, channel and shared file.
I created and validated the org-wide Company Announcements Team with Emily Wilson.