Proof we're not bluffing

This demo walks through remotely provisioning Android-based and SIP Teams phones in the Microsoft Teams admin center. From Teams devices > Phones, it uses Actions > Provision devices to add devices by uploading MAC addresses or entering them manually, then sets a location (Seattle in the example) and saves. Next it generates a verification code to share with the technician installing the device; once they use it, the phone appears under Waiting for sign-in. The video notes remote provisioning doesn’t support personal accounts, so you sign in with a resource account via Sign in a user, wait for the sign-in to complete, and then confirm the device shows up in the main phones list ready for use. It also calls out that Windows-based devices are provisioned by entering credentials directly on the device.

We produced this as a workflow you can follow mid-deployment—scripted around the exact moments admins typically stall (MACs, verification code, waiting for sign-in). Clean screen capture and confident narration keep the steps unambiguous, and the edit stays lean so the process feels manageable at scale. Final delivery includes closed captions, audio description, and thumbnails.

This demo shows how to remotely sign in to Android-based and SIP Teams phones from the Microsoft Teams admin center. It starts in Teams devices > Phones, where you use the Display name column to spot Signed out devices, then filter to find devices that are signed out and online (offline devices can’t be signed in remotely). After selecting a device, you choose Sign in, copy the device code, and complete authentication at microsoft.com/devicelogin. The video notes that remote sign-in doesn’t support personal accounts—you’ll use a resource account—then shows signing out via Actions > Sign out, including the option to sign out multiple devices from the grid.

We produced this as a “do it while you watch it” demo: tight scripting, clear callouts to the one detail people always need (the device code), and an edit that keeps the pace moving without skipping the moments admins must wait for. The payoff is a smoother device rollout and fewer hands-on trips to hardware—plus final delivery with captions, audio description, and thumbnails.

This demo walks through checking the health of Teams devices in the Microsoft Teams admin center. It starts in Teams devices, then drills into device health indicators—showing how admins can spot issues quickly, review device status, and understand whether a device is healthy, needs attention, or is offline. The goal is to give admins a fast, reliable way to monitor meeting-room and phone hardware without needing to physically visit every device (a hobby no one asked for).

We produced this as a clarity-first admin walkthrough—clean screen capture, steady narration, and an edit that keeps the viewer oriented as you move through the device views and health signals. The result is a quick reference that helps teams troubleshoot faster and keep device fleets ready for meetings that actually start on time. Final delivery includes closed captions, audio description, and thumbnails.

This demo shows how to create and set up a new team in the Microsoft Teams admin center—from blank slate to ready-to-collaborate. In Teams > Manage teams, you select Add, name the team (Marketing Team in the example), and optionally fill in details. It recommends changing the default owner (the admin account you used to sign in) and assigns Adele Vance as owner instead, then opens the new team to add members. Finally, it creates a channel under Channels > Add, names it Social media planning, adds a description, and explains channel types: Standard, Private, and Shared—calling out that Shared channels can include external users. The example uses a Private channel with Adele as channel owner so only invited members can see it.

We produced this as a start-to-finish setup demo with a satisfying “now it’s real” arc: we scripted each step to match how admins actually work, captured crisp UI with professional voiceover and music, and edited it to keep momentum while still making the choices (owner, channel type, visibility) feel obvious. Final delivery includes closed captions, audio description, and thumbnails.

This demo shows how to assign policy packages in the Microsoft Teams admin center—so you can apply a curated bundle of policies to a user in one move instead of playing whack-a-mole across policy types. From Users > Manage users, it selects a user (Adele Vance), opens Policies, and uses the policy package option to choose a package (Frontline worker in the example). After assigning, the user inherits the package’s included policies, with a note that individual policy assignments can still override parts of a package when needed.

We produced this as a clean, “one action, big impact” admin demo: preproduction to map the shortest path and clarify what packages do, production to capture crisp UI with professional voiceover, and post to keep the flow tight so the concept and the clicks land together. Final delivery includes closed captions, audio description, and thumbnails.

This demo explains how to edit the org-wide meeting policy in the Microsoft Teams admin center—the Global [Org-wide default] policy that applies to all users by default. From Meetings > Meeting policies, it opens Global and walks through the major sections: general meeting feature toggles (with inline “More information” help), audio and video settings like IP audio/video, recording and transcription controls, content sharing options, and Participants & guests. The example change disables Let anonymous people join a meeting, then saves—meaning users without a more specific assigned policy will have meetings that block anonymous join.

We produced this as a policy-focused walkthrough that avoids the “wall of toggles” feeling. Preproduction prioritized the sections viewers actually need to understand, production captured clean screens with steady narration, and post kept the structure tidy so the impact of one change is unmistakable. As always, we deliver captions, audio description, and thumbnails for easy rollout and reuse.

This demo shows how to find specific Teams phones fast in the Microsoft Teams admin center—even when you’re managing hundreds. It starts in Teams devices > Phones, then uses quick filters from the Devices summary and Health summary cards, plus the view toggles for all phones vs user phones, common area phones, or conference phones. From there it demonstrates two search approaches: simple column search (for example, searching the Username column for Alex Wilber to see only his signed-in devices) and advanced filtering that combines multiple criteria—like Sign-in status = Signed-out and Manufacturer = AudioCodes—so you can narrow the grid to exactly the devices you need.

We produced this as a brisk, “hands on the wheel” admin demo: preproduction mapped the fastest routes to the right devices, production captured clean UI with professional voiceover and a steady pace, and post kept the flow tight while still showing the decision points (search vs filter, single vs multi-criteria). The result is a walkthrough that helps admins cut through device sprawl and get to answers quickly—with final delivery including closed captions, audio description, and thumbnails.

This demo clarifies a common Teams admin center confusion: policies vs settings. It explains that policies are bundles of configurable options you can apply to specific users or groups (Meetings > Meeting policies), and shows how to check who has a policy via View users or see group-based assignments under Group policy assignment (example: a custom policy assigned to the Sales and Marketing group). In contrast, settings apply tenant-wide—one switch affects everyone—demonstrated with a Meeting settings example: enabling Insert Quality of Service markers and saving to update the whole organization.

We produced this as a “mental model” demo—less button-mashing, more clarity that sticks. The narration and edit are built to help viewers categorize what they’re changing before they change it, which reduces accidental org-wide toggles and makes policy planning feel calmer and more intentional. Final delivery includes closed captions, audio description, and thumbnails.

This demo shows how to change a user’s voice settings in the Microsoft Teams admin center to control outbound calling and call answering behavior. From admin.teams.microsoft.com, it goes to Users > Manage users, selects a user (Adele Vance), and opens the Voice tab. It then walks through outbound calling options—Any destination, In the same country or region, or Don’t allow—and configures call answering rules, including ringing the user’s devices plus a second action like simultaneously ring a user or number, call delegation, or group call pickup. It also covers what happens if the user doesn’t answer (voicemail, forward to a person/number, group call pickup, or delegation), then saves the changes.

We produced this as a focused admin micro-demo: the clicks are intentional, the narration stays plain-English, and the pacing is tuned for “follow along and finish” rather than “watch and hope.” The result is a quick, reusable walkthrough that helps admins set clear calling guardrails and consistent call handling—delivered with closed captions, audio description, and thumbnails.

This demo shows how to create a custom Teams meeting policy and assign it to a group using the Microsoft Teams admin center. It starts in Meetings > Meeting policies, selects Add, names a new policy (Sales and Marketing meeting policy), and reviews the major configuration sections—General, Audio & video, Recording & transcription, Content sharing, and Participants & guests—then saves. Next it assigns the policy via Group policy assignment > Add, selects the target group (Sales and Marketing), sets a rank number to control precedence when users belong to multiple groups (lower number = higher priority), selects the policy to apply, and clicks Apply so group members inherit those meeting settings unless a higher-priority policy overrides them.

We produced this as a “build it, target it, control precedence” demo—structured so the concept (policy + rank) lands at the same time as the clicks. In production we captured clean UI with professional voiceover, and in post we kept it punchy while still slowing down at the two crucial steps: ranking and assignment. Final delivery includes closed captions, audio description, and thumbnails.

This demo walks through assigning a phone number to a user in the Microsoft Teams admin center. It opens admin.teams.microsoft.com, goes to Voice > Phone numbers, and uses Filter to narrow the list to unassigned numbers for easier selection. After choosing an available number, it selects Edit, searches for and assigns it to a user (Adele Vance), and selects an emergency location (required) for emergency services routing. It also calls out the option to email the user with their new phone number details (enabled by default), then applies the update and notes it can take a few minutes before the number is active.

We produced this as a clean, no-mystery walkthrough—tight scripting, crisp screen capture, and just enough context to prevent “why is this field mandatory?” detours. It’s built to help admins move fast while still getting the important details right, with final delivery including closed captions, audio description, and thumbnails.

This demo shows how to change Microsoft Teams policy assignments for multiple users at once in the Microsoft Teams admin center. It starts in Users > Manage users, where you select one or several people (Alex Wilbur, Megan Bowman, and Lynne Robbins in the example), then choose Edit settings to update policy assignments in bulk. In the side pane, you pick the policy types you want to change—like Meeting policy—and assign an available option such as Restricted Anonymous Access, while anything set to Keep existing policy stays untouched. Select Apply to save, and the selected users inherit the new policy assignment.

We produced this as a brisk admin walkthrough that’s built for repeatability: preproduction locked the exact clicks and the “don’t change what you don’t mean to” guardrails, production captured clean screens with professional voiceover and music, and post tightened the flow so viewers can mirror the steps in their own tenant without second-guessing. Final delivery includes closed captions, audio description, and thumbnails.