Skills Demonstrated
Shared Mailbox — Support HelpDesk
Microsoft 365 Admin Center → Teams & Groups → Shared mailboxes
Created and configured a shared mailbox at support@anish.website to simulate a real IT support team inbox. Added David Wilson and Sarah Smith as members, then validated end-to-end functionality — sending emails from the shared address and confirming receipt in a user inbox — all without requiring a dedicated licence for the mailbox itself.
support@anish.website provisioned in Microsoft 365 Admin Center under Shared mailboxes.
David Wilson and Sarah Smith granted Send As and full access permissions to the mailbox.
Test email sent from support@anish.website via Sarah Smith's account; received in David Wilson's inbox.
Opened shared mailbox inside Outlook alongside personal account — demonstrated parallel mailbox management.
Confirmed sent email appears in Support HelpDesk Sent Items folder, not the sender's personal account.
Shared mailbox operates without an assigned licence — cost-efficient for team email scenarios.
Screenshots — Shared Mailbox Setup & Testing
Shared mailbox "Support HelpDesk" (support@anish.website) successfully created — M365 Admin Center confirms creation with next steps to add members
David Wilson and Sarah Smith added as shared mailbox members — both can send and receive on behalf of support@anish.website
Support HelpDesk Sent Items showing the test email to David Wilson — stored in the shared mailbox, not in the sender's personal account
David Wilson's inbox confirms receipt of the test email from Support HelpDesk — end-to-end shared mailbox flow validated
David Wilson's Outlook showing multiple linked accounts — demonstrates real-world multi-tenant identity management in a single client
Key Takeaway — Shared Mailboxes
- Shared mailboxes allow multiple users to manage a single email address without purchasing an additional licence — ideal for support teams and department inboxes
- Members with "Send As" permission send emails that appear from the shared address, not their personal account — keeping communications professional and consistent
- Sent Items are stored in the shared mailbox folder, giving the whole team visibility of outgoing correspondence
- Testing via two separate Outlook sessions (shared mailbox + recipient) is the correct approach to verify full send-and-receive functionality
Resource Mailbox — Room Booking
Exchange Admin Center → Recipients → Resources
Created a Room resource mailbox (Board Room) via the Exchange Admin Center to enable calendar-based meeting room bookings. Configured auto-accept booking options, then tested the full workflow — booking the room from David Wilson's Outlook calendar and verifying the room's acceptance confirmation reply.
Board Room mailbox (boardroom@anish.website) provisioned in Exchange Admin Center with booking options configured.
Created a "Team Meeting" event from David Wilson's Outlook calendar, inviting the Board Room as a resource.
Board Room sent an automatic acceptance reply — David Wilson's calendar updated with confirmed room booking.
Screenshots — Resource Mailbox & Room Booking
Exchange Admin Center confirms "Resource mailbox creation successful!" after completing all four setup steps: Resource Setup, General Information, Booking options, and Review
New event created with Board Room (boardroom@anish.website) added as a resource — availability shows as "Available" for the 7:00–7:30 PM slot
David Wilson's inbox shows "Board Room accepted" — the Team Meeting is confirmed on both the user's calendar and the room's calendar for Wed 27 May, 7:00–7:30 PM
Key Takeaway — Resource Mailboxes
- Resource mailboxes (Rooms & Equipment) allow physical spaces and assets to be booked directly through Outlook — no manual coordination required
- The auto-accept feature means the room responds instantly when available, streamlining meeting scheduling across the organisation
- Room bookings appear on both the attendee's calendar and the resource mailbox calendar, providing a single source of truth for facility management
- Resource mailboxes are managed through Exchange Admin Center and do not require separate user licences
SharePoint Site — IT Team Department
SharePoint Admin Center → Active sites → IT Internal Department
Provisioned a private SharePoint team site ("IT Internal Department") for the IT team's internal file storage. Configured a three-tier permission model (Members, Owners, Visitors), created a confidential document library folder with unique restricted permissions, uploaded an IT policy document, and tested external document sharing — all through SharePoint's modern permission management interface.
IT Internal Department SharePoint site created as a private group from SharePoint Admin Center.
Three-tier model: Members (Edit), Owners (Full Control), Visitors (Read) applied at the site level.
"Confidential – HR only" folder created with unique permissions breaking inheritance from the site.
IT policy.docx uploaded to the Documents library and made available to site members.
IT policy.docx shared with an external Gmail account — sharing invitation confirmed.
Users assigned to SharePoint groups (Sarah Smith as Member, David Wilson as Visitor) via the Permissions panel.
Screenshots — SharePoint Site & Permission Configuration
SharePoint Admin Center showing IT Internal Department site details — private group with primary email ITInternalDepartment@anish.website, created 27 May 2026
Classic SharePoint site permissions page showing three groups: IT Team Department Members (Edit), IT Team Department Owners (Full Control), IT Team Department Visitors (Read)
Classic SharePoint People and Groups view showing IT Team Department Owners group — demonstrating the three-group structure (Members, Visitors, Owners) in the left navigation
SharePoint Documents library showing the "Confidential – HR only" folder created inside the IT Team Department site
Documents library with the Permissions panel open — Sarah Smith (Edit) and David Wilson (Read) assigned, confirming the three-tier access model applied at site level
Confidential folder shows "This folder has unique permissions" — inheritance broken from the parent site, applying a separate access control list for HR-sensitive content
IT policy.docx shared externally — confirmation dialog shows anishhgirii@gmail.com has been invited to view the document, demonstrating SharePoint's external sharing capability
Key Takeaway — SharePoint Permissions & Document Management
- SharePoint's three-group model (Members/Owners/Visitors) maps directly to Edit, Full Control, and Read access — implementing least-privilege principles at the site level
- Breaking permission inheritance on a folder allows sensitive content (e.g. HR documents) to have a completely separate access control list, invisible to general site members
- External sharing can be scoped to individual files or folders — administrators control whether links are view-only, editable, or require sign-in
- SharePoint integrates natively with Microsoft 365 Groups, Teams, and Exchange — a site provisioned from the SharePoint Admin Center automatically creates a corresponding group email and Teams channel