How to Configure Teams Dial-In Audio Conferencing Users in PowerShell Using Set-CsOnlineDialInConferencingUser

In modern enterprise collaboration, audio conferencing bridges provide a vital lifeline for mobile workers, field staff, and external partners joining Microsoft Teams meetings from environments without stable internet connectivity. When users schedule meetings with Audio Conferencing licenses enabled, Microsoft Teams automatically embeds a local dial-in phone number and dynamic conference ID into the meeting invitation. Beyond the basic dial-in number, meeting organisers often require customized conferencing settings—such as personalised dial-in PINs for phone-based meeting initiation, dedicated toll or toll-free bridge numbers, and custom participant entry/exit announcement chime policies.

While the Microsoft Teams Admin Centre allows basic user-by-user configuration, enterprise administrators managing large user cohorts or enforcing standardised dial-in profiles rely on the Microsoft Teams PowerShell module. The Get-CsOnlineDialInConferencingUser and Set-CsOnlineDialInConferencingUser cmdlets provide programmatic control over conferencing bridge settings, user PIN lifecycles, and audio prompts. This guide covers how to inspect user conferencing attributes, reset organiser PINs, assign dedicated dial-in telephone numbers, and automate conferencing configurations across an organisation.

Understanding Teams Dial-In Audio Conferencing Architecture

Audio Conferencing in Microsoft Teams connects the traditional Public Switched Telephone Network (PSTN) to Microsoft’s cloud meeting infrastructure via shared or dedicated dial-in bridges. The user-level conferencing profile governs several critical interaction points:

• Conferencing Bridge Number (ServiceNumber): The default telephone number (toll or toll-free) inserted into the meeting organizer’s Outlook calendar invites. Users calling from specific geographical locations can be assigned local numbers matching their office region.
• Organiser Dial-in PIN: A numeric security code required by the meeting organizer when joining their own meeting via telephone before any computer-based participants have joined. Entering the correct PIN promotes the caller to the meeting leader role, unlocks the lobby, and initiates audio recording if configured.
• Entry and Exit Announcements: Governs whether a chime sounds or the participant’s recorded name is announced when someone joins or leaves the dial-in audio conference.
• Conference ID Type: Determines whether the organizer uses dynamic, randomly generated conference IDs for each meeting or a persistent static conference ID.

Connecting to Teams PowerShell and Auditing Current Users

To configure audio conferencing settings, launch an elevated PowerShell console and authenticate with Microsoft 365 tenant administrator credentials:

# Import module and authenticate to Microsoft Teams
Import-Module MicrosoftTeams
Connect-MicrosoftTeams

To inspect the active dial-in conferencing configuration for a specific licensed user, execute Get-CsOnlineDialInConferencingUser:

# Retrieve dial-in conferencing profile for a user
Get-CsOnlineDialInConferencingUser -Identity "[email protected]"

The resulting object displays the user’s assigned bridge parameters:

Identity                    : [email protected]
ServiceNumber               : +442038555123
TollNumber                  : +442038555123
TollFreeNumber              : 
ConferenceId                : 819234123
IsPinned                    : True
Pin                         : ********
EntryExitAnnouncementsType  : Chime
AutomaticLobbyBypass        : True

Resetting and Managing Organizer Dial-In PINs

If an organizer forgets their audio conferencing PIN or suspects it has been compromised, administrators can generate a new secure numeric PIN or assign a temporary one via PowerShell:

Generating a Random Secure PIN Automatically

To trigger an automatic PIN reset that sends an email notification with the newly generated PIN directly to the user’s inbox:

# Automatically generate a new random PIN and notify user via email
Set-CsOnlineDialInConferencingUser -Identity "[email protected]" -ResetPin -SendEmail $True

Specifying a Custom Numeric PIN Directly

In environments where an automated ticketing system provisions temporary credentials, you can specify an explicit PIN (must comply with tenant PIN length requirements, typically 5–12 digits):

# Assign an explicit numeric PIN to the user
Set-CsOnlineDialInConferencingUser -Identity "[email protected]" -Pin "847291" -SendEmail $False

Assigning Dedicated Bridge Phone Numbers

Organizations with offices spread across multiple regions often want meeting invitations to feature local regional dial-in numbers rather than default corporate headquarters numbers. To view all available conferencing bridge numbers configured on the tenant:

# List available toll and toll-free conferencing service numbers
Get-CsOnlineDialInConferencingServiceNumber | Select-Object Number, City, CountryOrRegion, BridgeName

Once you have identified the appropriate local service number, assign it to the user’s conferencing profile:

# Assign a specific regional toll dial-in number
Set-CsOnlineDialInConferencingUser -Identity "[email protected]" `
    -ServiceNumber "+441618555456" `
    -SendEmail $True

Future meeting invites scheduled by this user will automatically feature the specified Manchester phone number as the primary dial-in option.

Configuring Entry and Exit Announcement Policies

Participant entry and exit chimes help organizers track meeting attendance. However, for large town halls or webinar-style calls, frequent chimes can be highly disruptive. The -EntryExitAnnouncementsType parameter controls this behaviour:

• Chime: Plays a brief, unobtrusive audio tone whenever a caller connects or disconnects.
• Name: Prompts callers to record their name, which is then spoken into the conference upon joining.
• Off: Disables all entry and exit audio notifications for silent join experiences.

To disable announcements for an executive user who frequently hosts large conference calls:

# Disable entry and exit announcements for the organizer
Set-CsOnlineDialInConferencingUser -Identity "[email protected]" `
    -EntryExitAnnouncementsType Off

Automating Audio Conferencing Configuration for Regional Departments

To ensure consistent configuration across entire office locations, import a list of regional employees from a CSV file and batch-configure their dial-in service numbers and announcement settings:

# Bulk configure regional audio conferencing settings from CSV
$Users = Import-Csv -Path "C:\Admin\ManchesterUsers.csv"

foreach ($User in $Users) {
    Write-Host "Updating conferencing profile for $($User.UserPrincipalName)..." -ForegroundColor Cyan
    try {
        Set-CsOnlineDialInConferencingUser -Identity $User.UserPrincipalName `
            -ServiceNumber "+441618555456" `
            -EntryExitAnnouncementsType Chime `
            -SendEmail $False `
            -ErrorAction Stop
        Write-Host "Updated $($User.UserPrincipalName) successfully." -ForegroundColor Green
    }
    catch {
        Write-Warning "Failed to update $($User.UserPrincipalName): $_"
    }
}

Troubleshooting Common Dial-In Conferencing Issues

When users encounter difficulties with audio conferencing bridges, check these common diagnostic factors:

• Missing Audio Conferencing License: If Set-CsOnlineDialInConferencingUser throws an error stating that the user is not found or not enabled for audio conferencing, verify that an active Microsoft 365 Audio Conferencing add-on license is assigned to the account in Microsoft Entra ID.
• Toll-Free Bridge Dial-Out Credit Restrictions: If participants are unable to dial into a toll-free number, verify that your tenant has active Communications Credits or Pay-As-You-Go calling enabled, as toll-free usage draws against prepaid balances.
• PIN Propagation Delay: When resetting a user’s PIN via PowerShell, allow up to 15 minutes for the new PIN to synchronize across all global Teams PSTN gateway nodes before attempting phone authentication.
• Static vs Dynamic Conference IDs: If external callers report that old meeting links join incorrect conference calls, reset the user’s conference ID to dynamic generation using Clear-CsOnlineDialInConferencingUser -Identity $User -ResetConferenceId.

Using PowerShell to administer Teams dial-in conferencing ensures reliable, secure, and geographically optimised telephone access for meeting organizers and participants across the enterprise.