You’re stuck mid-meeting when Teams freezes, and you need to know right now whether Microsoft’s service is down or your setup’s broken. That distinction matters because restarting your computer 12 times won’t fix a datacenter outage. This guide walks through the fastest, most reliable ways to check service status before you waste time troubleshooting problems that aren’t yours to fix.

Quick Methods to Check if Microsoft Teams is Down

Before you start troubleshooting, figure out whether Microsoft Teams is actually experiencing a service-wide outage or if the problem’s just on your end. This saves you hours of unnecessary fixes. When Teams stops working, verification through official status channels should always be your first step, not clearing cache or reinstalling the app.

1. Microsoft 365 Service Health Portal (Admin Access)

If you’ve got admin access to your organization’s Microsoft 365 tenant, the Service Health portal at https://admin.microsoft.com/Adminportal/Home#/servicehealth gives you the most detailed view of service outages. This dashboard shows real-time status for all Microsoft 365 services including Teams, Exchange Online, SharePoint, and Azure Active Directory. Admin users can see incident reports with specific error codes, affected features, resolution timelines, and datacenter issues that might only impact certain geographic regions. The portal also shows whether Microsoft’s actively investigating or restoring service. Something like “We’re actively investigating reports of users being unable to join meetings” means there’s a confirmed service outage.

2. Public Office 365 Status Page

Visit https://status.office365.com as your first step to check Office 365 apps status and identify service-wide outages. On August 2nd, Microsoft Teams users in Europe reported widespread connection failures, which status.office365.com confirmed as a service interruption within 12 minutes. This public page doesn’t need admin credentials and displays current service health for Teams, Outlook, SharePoint, and other Microsoft 365 applications. It updates every few minutes during active incidents and gives you basic information about which services are affected and estimated resolution times.

3. Downdetector Real-Time Community Reporting

Check if Microsoft Teams is experiencing outages using Downdetector or Microsoft Service Status page before troubleshooting local issues. Downdetector aggregates user reports in real time, showing geographic heat maps of where problems are occurring and trending keywords in user comments. When hundreds of reports spike within minutes, it’s strong evidence of a service-wide issue. The platform shows if problems are concentrated in meetings, messaging, or calling features, helping you understand whether the entire service is affected or just specific functionality.

4. Twitter Status Account Monitoring

Monitor the @MSFT365Status Twitter account for real-time Microsoft 365 service updates. The @MSFT365Status account reports issues more frequently than the official @MicrosoftTeams account, often posting incident acknowledgments before they appear on status dashboards. The @MicrosoftTeams Twitter account focuses primarily on feature announcements rather than outage reporting, making it less useful for status verification. During major incidents, @MSFT365Status provides updates every 30 to 60 minutes with progress reports and resolution estimates.

5. Azure Active Directory Status Page

Azure Active Directory outages can affect Microsoft Teams due to service interdependencies. Since Teams relies on Azure AD for authentication, sign-in problems often originate from backend identity services rather than Teams infrastructure itself. Check the Azure status page at https://status.azure.com to see if authentication services are experiencing issues, particularly when you encounter login credentials errors or “cannot connect” messages across multiple Microsoft 365 applications simultaneously.

Each verification method reveals different aspects of service health. The Service Health portal shows tenant specific incidents and advisory notifications. The public Office 365 status page confirms global service disruptions. Downdetector indicates whether other users are experiencing identical symptoms in real time. Twitter provides immediate incident acknowledgment before official channels update. Azure status identifies authentication layer problems that show up as Teams failures.

Dashboard Status Indicators Explained:

Service degradation means Teams is functioning but with reduced performance, slower message delivery, or intermittent connection drops.

Service interruption means core functionality is unavailable for a subset of users, such as inability to join meetings or send messages.

Restoring service means Microsoft has identified the root cause and is actively implementing fixes across affected datacenters.

Investigating issues means Microsoft has confirmed user reports and is diagnosing the problem but hasn’t determined the cause yet.

Extended recovery means service restoration is taking longer than expected, often due to complex backend issues requiring phased rollouts.

Incident reports on the Service Health dashboard include tracking numbers, affected feature lists, user impact estimates, and root cause analysis once available. Resolution timelines show whether Microsoft expects fixes within hours or days. Azure Active Directory status directly impacts Teams functionality, so an “Investigating” status for Azure AD authentication services means Teams sign-in problems are expected. Datacenter specific issues may only affect certain geographic regions, explaining why some team members connect successfully while others in different locations can’t. During a June outage, North American users experienced complete service interruption while European users maintained full functionality throughout the incident.

Common Microsoft Teams Connection Issues and Error Messages

Microsoft Teams outages can result from patches or updates that don’t perform as expected. When Microsoft deploys updates across its global infrastructure, unforeseen compatibility issues or configuration errors can temporarily disrupt service. Distinguishing between these service-wide incidents and localized problems saves time and directs troubleshooting efforts appropriately.

If no service-wide issues are reported on official channels, the problem’s likely localized to individual users. These isolated incidents typically stem from network configurations, outdated application versions, corrupted local cache, or device specific settings. Azure Active Directory outages can affect Microsoft Teams due to service interdependencies, meaning authentication failures that appear to be Teams problems are actually backend identity service disruptions.

Azure Active Directory issues often show up as Teams connection problems because every Teams operation requires valid authentication tokens. When Azure AD experiences service degradation, users see sign-in loops, persistent “Cannot connect” errors, or Teams loading indefinitely at the splash screen. These symptoms look identical to network problems but affect all Microsoft 365 applications simultaneously. If Outlook and SharePoint also fail to load while non-Microsoft services work fine, the root cause is almost certainly Azure AD rather than Teams specific infrastructure.

Complete Local Troubleshooting and Diagnostic Process

After verifying no widespread outage is reported through official Microsoft status channels, Downdetector, or social media monitoring, begin systematic local troubleshooting to isolate device specific, network specific, or configuration specific problems.

Network and Connection Diagnostics

Test internet connection stability and switch to wired Ethernet connection for better call quality and reduced lag. Wireless connections introduce packet loss and latency spikes that disrupt real-time communication.

Verify Teams-related domains and ports are allowed on network firewall for calling functionality, particularly if corporate firewalls block UDP traffic required for audio and video streams.

Identify VPN interference by temporarily disabling VPN clients and testing Teams connectivity, as some VPN configurations route traffic through congested servers or block WebRTC protocols.

Check local network settings including DNS server configuration, proxy settings, and whether network adapter drivers need updates.

Understand bandwidth requirements for different Teams features. Audio calls need 100 Kbps, video calls require 1.5 Mbps, and screen sharing with video needs 4 Mbps.

Verify meeting organizer permissions under Meeting Options if unable to share screen during meetings, as organizers can restrict presenter capabilities for participants.

Review firewall rules to ensure outbound connections to *.teams.microsoft.com, *.skype.com, and *.microsoft.com domains are permitted without SSL inspection.

Windows includes built-in network diagnostics accessible through Settings > Network & Internet > Status > Network troubleshooter that automatically detects and repairs common connection issues. Run ping tests to Microsoft servers using Command Prompt with “ping teams.microsoft.com” to verify DNS resolution and basic connectivity. Use traceroute with “tracert teams.microsoft.com” to identify where connection paths fail, showing whether problems occur within your local network, at your ISP, or reaching Microsoft datacenters.

Application-Level Troubleshooting Steps

1. Restart Teams application by right-clicking the system tray icon and selecting Quit, then reopening from the Start menu.

2. Restart computer to clear memory leaks, reset network adapters, and ensure Windows updates take effect.

3. Clear Teams cache by navigating to C:\Users\YourUsername\AppData\Roaming\Microsoft\Teams and deleting folder contents to resolve corruption issues. This removes stored credentials, meeting history, and cached files forcing Teams to rebuild its local database.

4. Disable GPU hardware acceleration in Settings > General if Teams experiences lag or performance issues, particularly on older graphics cards or systems with outdated GPU drivers.

5. Check for Teams updates through Settings > About > Check for updates, as Microsoft frequently releases patches addressing specific bugs and performance problems.

6. Clear browser cookies for web version users experiencing persistent sign-in loops or session timeout errors.

7. Update Teams mobile app via Google Play Store or App Store and check device permissions for microphone and camera access in iOS Settings > Teams or Android Settings > Apps > Teams > Permissions.

8. Uninstall and reinstall Teams from Windows Settings > Apps if cache clearing doesn’t resolve persistent issues. Complete removal eliminates corrupted installation files.

System Resource and Compatibility Checks

Use Task Manager (Ctrl+Shift+Esc) to monitor Teams resource consumption including CPU percentage, memory usage, disk activity, and network bandwidth. Teams typically uses 200 to 400 MB of memory during idle operation and spikes to 1 to 2 GB during video meetings. If CPU usage exceeds 50% consistently or memory grows beyond 2 GB, resource exhaustion is causing performance degradation. Check for background processes consuming resources, insufficient RAM (Teams requires 4 GB minimum, 8 GB recommended), or hard drive fragmentation on older mechanical drives.

Supported operating systems for desktop include Windows 10 version 1809 or later, macOS 10.13 High Sierra or newer. Older OS versions lack security features and WebRTC implementations required for modern Teams functionality.

Supported browsers for web version are Microsoft Edge, Google Chrome, Safari 14+, and Firefox 78+ with specific limitations on screen sharing in Firefox.

Mobile OS version requirements mandate iOS 14.0 or later and Android 8.0 or higher for full feature access including background notifications and call hand-off.

Third-party plugin conflicts from browser extensions or desktop applications that intercept network traffic or inject code into Teams processes.

GPU hardware acceleration compatibility issues on systems with Intel integrated graphics older than 6th generation or AMD graphics from before 2016.

If these comprehensive steps don’t resolve the issue after confirming no service outage exists, IT department contact is warranted for investigation of network policies, tenant configuration, or licensing problems beyond individual user control. Outdated systems or incompatible configurations can mimic outage symptoms, particularly when security software blocks specific Teams features or corporate policies restrict functionality without clear error messages explaining the restrictions.

Feature-Specific Problems and Outage Identification

Distinguishing feature specific problems from service-wide outages requires understanding that Teams operates as multiple interconnected services rather than a single application. Calling infrastructure is separate from chat messaging. File sharing depends on SharePoint and OneDrive. Meeting coordination relies on Exchange calendar integration.

Calling and Meeting Feature Issues

Calling and meeting features have separate infrastructure components from persistent chat and file collaboration. Microsoft’s global voice network runs on different servers than messaging services, meaning voice calls can fail while chat works perfectly or vice versa. Teams Calling requires additional licensing and phone number assignment through organization administrators. Attempting to make calls without proper licensing produces “Feature not enabled” errors that resemble service outages.

Verify Teams Calling licensing and phone number assignment through your organization’s admin center to confirm calling capabilities are activated for your account.

Device selection checks in Settings > Devices ensure the correct microphone, speaker, and headset are selected for audio troubleshooting. Windows often switches default devices when USB headsets connect or Bluetooth devices pair.

Noise suppression settings available in Teams Settings > Devices with Auto, High, or Low options reduce background noise using AI processing that sometimes causes audio artifacts or latency.

Camera access must be enabled in Windows Settings > Privacy & security > Camera with the toggle switched on for Teams, then select correct camera in Teams Settings > Devices.

Screen sharing meeting organizer permissions configured under Meeting Options control whether participants can share screens or only designated presenters have that capability.

Connection quality indicators displayed during active calls show packet loss, latency, and bandwidth metrics that reveal network level problems distinct from service outages.

Network specific requirements for Teams calling include stable internet connections with consistent low latency. Test internet connection stability and switch to wired Ethernet connection for better call quality and reduced lag. WiFi introduces variable latency and packet loss during congestion or when multiple devices compete for bandwidth. Verify Teams-related domains and ports are allowed on network firewall for calling functionality, particularly UDP ports 3478 to 3481 used for media traffic. Corporate firewalls that block UDP force Teams into TCP fallback mode with degraded audio quality. Bandwidth requirements escalate with feature usage. One-to-one video calls need 1.5 Mbps while group video meetings with gallery view require 4 Mbps upload and download speeds.

File Sharing and Collaboration Feature Problems

Teams dependency on SharePoint and OneDrive for file operations means file sharing failures often originate from backend storage services rather than Teams infrastructure itself. When users report inability to upload or access files, check SharePoint and OneDrive status separately from Teams status because these services can experience independent outages.

Teams has a file size upload limit of 250 GB for file sharing through SharePoint backed channels, while chat file attachments route through OneDrive with different size restrictions and storage quota enforcement.

When multiple users report identical feature failures across calling, meetings, or file sharing, service-wide outages are likely affecting specific Teams infrastructure components rather than isolated configuration incidents. If five colleagues simultaneously can’t join meetings but chat works normally, meeting coordination services are experiencing problems. Conversely, when one user can’t share screen but others in the same meeting have no issues, the problem’s localized to that user’s device permissions or network configuration. Check SharePoint and OneDrive status separately from Teams status when file operations fail, as these backend services can experience independent outages that show up as Teams file sharing problems without affecting messaging or calling features.

What Different Teams Outage Types Mean

Microsoft Teams experiences several distinct categories of service disruptions, each with different causes, user impacts, and expected resolution timeframes.

Scheduled Maintenance Windows

Planned downtime notifications appear in the Service Health dashboard days in advance, typically scheduled during low usage periods like weekends or late nights in specific time zones. Microsoft performs backend infrastructure updates, database migrations, and datacenter maintenance that requires brief service interruptions. These maintenance windows usually last 2 to 4 hours and affect specific features rather than disabling Teams entirely. Users receive advance notification through email and admin center messages stating which features will be unavailable and exact start and end times.

Regional Service Disruptions

Geographic specific issues affect users in particular datacenter regions while other regions maintain full functionality. When Azure infrastructure in West Europe experiences problems, users connecting through those datacenters see connection failures and degraded performance while North American and Asian users continue working normally. Regional outages often stem from datacenter network equipment failures, power distribution problems, or localized internet backbone issues. Microsoft status pages indicate affected regions explicitly, and resolution involves traffic redirection to healthy datacenters before fixing underlying infrastructure problems, typically resolving within 1 to 4 hours.

Unplanned Global Interruptions

Widespread failures from patches or backend problems constitute the most severe outage type, affecting users worldwide simultaneously. Microsoft Teams outages can result from patches or updates that don’t perform as expected, such as configuration changes that cascade across global infrastructure or authentication service failures in Azure Active Directory. These incidents generate massive spikes in Downdetector reports and social media complaints as millions of users lose access. Microsoft escalates to highest priority response teams, provides frequent status updates every 30 minutes, and often implements rollbacks of recent changes while investigating root causes. Global interruptions typically resolve within 2 to 6 hours but can extend longer for complex backend issues requiring careful database repairs or configuration corrections across hundreds of servers.

Desktop Client Versus Web and Mobile Teams Apps

Testing multiple Teams platforms helps identify platform specific issues versus service-wide outages by isolating whether problems stem from a particular client implementation or affect the core Teams service infrastructure.

Quickly test the web version at teams.microsoft.com in different browsers to rule out desktop client problems. Launch Microsoft Edge, Google Chrome, and Firefox, then sign in to Teams through each browser to determine if the issue persists across platforms. If the desktop application shows connection errors but the web version works perfectly in all browsers, the problem’s isolated to the desktop client installation, corrupted cache at C:\Users\YourUsername\AppData\Roaming\Microsoft\Teams, or conflicts with desktop security software. Conversely, if all browsers display identical connection failures matching the desktop client symptoms, the issue likely originates from network restrictions, authentication problems, or actual service outages affecting backend infrastructure.

Testing the mobile app on iOS or Android provides another isolation vector since mobile clients use different network paths and authentication flows than desktop applications. Update Teams mobile app via Google Play Store or App Store and check device permissions for microphone and camera access in device Settings. Mobile apps connect through cellular networks that bypass corporate firewalls and VPN configurations affecting desktop clients. Successfully joining meetings from a mobile device while desktop and web versions fail indicates network policy restrictions rather than service outages. Mobile specific failures when other platforms work suggest app update requirements, device permission restrictions, or mobile operating system compatibility issues.

When platform specific failures suggest local issues versus service outages, the pattern of which clients work versus which fail reveals root causes. Desktop only failures point to Windows or macOS configuration problems, antivirus interference, or outdated desktop client versions. Web only failures in a single browser indicate browser extension conflicts or outdated browser versions. Mobile only failures suggest device permissions or mobile OS version requirements. When all three platforms (desktop, web, and mobile) display identical symptoms simultaneously, service-wide outages affecting core Teams infrastructure are extremely likely, and further local troubleshooting becomes unproductive until Microsoft resolves backend issues.

Using Social Media and Community Forums to Check Teams Status

Crowd-sourced reporting through social media and community forums often provides faster outage alerts than official Microsoft status channels because thousands of affected users report problems immediately when they occur. Corporate status pages update only after internal incident validation, escalation through support tiers, and official acknowledgment processes that can take 15 to 30 minutes after users first experience problems.

Social media monitoring offers real-time visibility into emerging incidents through unfiltered user reports describing exactly what isn’t working. Microsoft’s official channels sometimes delay public acknowledgment while investigating whether reported issues constitute genuine widespread service failures versus localized configuration problems or network issues affecting specific customer segments.

1. @MSFT365Status Twitter account provides real-time Microsoft 365 service updates with incident acknowledgments, progress reports every 30 to 60 minutes during active outages, and resolution confirmations. The @MSFT365Status account reports issues more frequently than the official @MicrosoftTeams account, often posting incident notifications before they appear on status dashboards.

2. @MicrosoftTeams account limitations mean this official handle focuses primarily on feature announcements rather than outage reporting, posting primarily about new capabilities, user tips, and product marketing rather than service disruptions.

3. Microsoft Tech Community forums at techcommunity.microsoft.com host detailed user discussions where affected users describe specific error messages, symptoms, and troubleshooting attempts, often revealing patterns that help distinguish service outages from configuration issues.

4. Reddit communities including r/MicrosoftTeams and r/Office365 where users report issues with timestamps and geographic locations, creating real-time outage maps through comment patterns showing “Can’t connect from Toronto” or “Meetings down in London since 10:15 AM.”

Correlating multiple user reports to confirm widespread outages requires looking for patterns rather than isolated complaints. When dozens of users across different organizations, geographic regions, and network configurations report identical symptoms within a 10 to 15 minute window, service-wide outages are extremely likely. Single reports or complaints spread over hours suggest localized issues. Geographic clustering of reports indicates regional datacenter problems. Feature specific complaints concentrated around calling or meetings while messaging works normally suggest infrastructure problems in specific service components. Social media provides the fastest confirmation when official channels lag, but verification through Microsoft’s status pages remains essential before assuming service-wide outages rather than coincidental local problems.

When to Contact Your IT Department About Teams Issues

The IT department has access to tenant level diagnostics unavailable to regular users, including service health dashboards showing organization specific incidents, user activity logs, licensing status, and backend configuration settings controlling Teams functionality.

Situations requiring IT intervention extend beyond individual troubleshooting capabilities when problems stem from organizational configuration rather than service outages or local device issues. Verify Teams Calling is enabled for your account and phone numbers are correctly assigned through organization licensing. Individual users can’t modify their own licensing status or calling capabilities. Check OneDrive or SharePoint connection and permissions when unable to access or open shared files, as document library permissions and sharing policies require administrator adjustment. Tenant specific configuration including conditional access policies, data loss prevention rules, and information barriers can restrict Teams functionality without generating clear error messages explaining why specific features are unavailable.

What information to provide IT includes detailed documentation of troubleshooting steps already attempted, exact error messages with screenshots capturing error codes and failure descriptions, timestamps showing when issues first occurred, and whether problems affect only you or multiple colleagues simultaneously. IT departments need to know if you’ve already cleared cache, tested web versus desktop clients, verified internet connectivity, and checked Microsoft status pages. This documentation prevents redundant basic troubleshooting and accelerates investigation of complex tenant level problems. Include details about what you were doing when the failure occurred (joining a meeting, uploading a file, initiating a call) because activity context helps IT isolate which backend services are involved.

Alternative communication methods when Teams is down:

Email through Outlook or Gmail for non-urgent messages and file attachments up to 25 MB.

Phone calls to team members using desk phones or mobile devices bypassing digital collaboration tools entirely.

SMS text messaging for urgent notifications when immediate response is required but Teams is unavailable.

Backup collaboration tools like Slack, Zoom, or Google Meet if your organization maintains redundant communication platforms.

IT can view tenant status and incident reports in the admin center at admin.microsoft.com showing service health details invisible to regular users. The Service Health dashboard displays incidents affecting your specific tenant, advisory notifications about planned maintenance, and historical incident reports with root cause analysis. IT administrators receive email notifications about service disruptions before they’re publicly announced, often learning about emerging incidents 10 to 20 minutes ahead of general user awareness. Visit Microsoft 365 Service Health page to verify organization-wide outages before extensive troubleshooting, ensuring IT can confirm whether reported problems match known incidents or require deeper investigation into tenant specific configuration.

Final Words

Knowing how to tell if Microsoft Teams is down starts with checking official status channels before diving into lengthy troubleshooting.

The Microsoft 365 Service Health portal and status.office365.com give you confirmed outage information fast. Downdetector and @MSFT365Status on Twitter fill in real-time gaps when official updates lag.

If the service shows green but you’re still stuck, work through network checks, cache clearing, and app restarts systematically.

Testing multiple platforms (desktop, web, mobile) helps isolate the problem quickly. When in doubt, your IT department has tenant-level tools and licensing access you don’t.

Stay methodical, verify first, troubleshoot second.

FAQ

Is Teams having issues right now?

Microsoft Teams may be having issues right now if the official Microsoft 365 Service Health portal at status.office365.com shows service degradation or if Downdetector displays a spike in user reports. Check both sources and the @MSFT365Status Twitter account for real-time confirmation of service-wide outages.

How to check if Microsoft Teams is working?

Microsoft Teams working status can be checked by visiting status.office365.com for public status updates, accessing the Microsoft 365 Service Health portal with admin credentials for detailed tenant information, or monitoring Downdetector for community-reported issues. Testing the web version at teams.microsoft.com provides immediate confirmation of service availability.

How to check Teams service status?

Teams service status can be checked through the Microsoft 365 Service Health portal for administrators, the public status page at status.office365.com for non-admin users, Downdetector for real-time community reporting, and the @MSFT365Status Twitter account for official service updates. Azure Active Directory status should also be verified since authentication issues directly impact Teams functionality.

Why is Microsoft Teams not working?

Microsoft Teams may not be working due to service-wide outages from patches or updates, Azure Active Directory authentication failures, local network connectivity issues, firewall blocking Teams domains and ports, or outdated application versions. Distinguish between service outages affecting all users and localized problems by checking status.office365.com before troubleshooting individual device or network configurations.

What does service degradation mean on Teams status page?

Service degradation on the Teams status page means Teams is experiencing reduced performance or limited functionality affecting some users, but the service remains partially operational. This indicator suggests slower loading times, delayed message delivery, or intermittent connection issues rather than complete service unavailability.

How do I clear Microsoft Teams cache?

Microsoft Teams cache can be cleared by navigating to C:\Users\YourUsername\AppData\Roaming\Microsoft\Teams and deleting the folder contents after closing Teams completely. This troubleshooting step resolves corruption issues causing performance problems, login failures, or message syncing errors.

Can firewall settings block Microsoft Teams?

Firewall settings can block Microsoft Teams if Teams-related domains and required ports are not allowed through the network configuration. Verify firewall rules permit Teams traffic for calling functionality and meeting connectivity, especially in corporate or restricted network environments where security policies limit outbound connections.

What is the difference between regional and global Teams outages?

Regional Teams outages affect users in specific geographic areas due to datacenter-specific issues, while global outages impact all users worldwide from backend infrastructure failures or widespread patch problems. Regional disruptions typically resolve faster and Microsoft routes traffic to unaffected datacenters when possible.

Should I use Teams desktop or web version during outages?

Testing both Teams desktop and web version at teams.microsoft.com during suspected outages helps isolate platform-specific issues from service-wide problems. If the web version works but desktop fails, the problem is likely local cache corruption or application configuration rather than a Microsoft service outage.

How long do Microsoft Teams outages typically last?

Microsoft Teams outages typically last from minutes to several hours depending on severity, with scheduled maintenance windows communicated in advance and unplanned interruptions resolved based on complexity. Check the Service Health portal for resolution timelines and incident reports providing estimated restoration times for active service disruptions.

Why does Azure Active Directory affect Microsoft Teams?

Azure Active Directory affects Microsoft Teams because Teams relies on Azure AD for user authentication, authorization, and identity management. Azure AD outages prevent Teams login, disable presence indicators, and block access to meetings and chats since the authentication backend becomes unavailable.

When should I contact IT about Teams problems?

Contact IT about Teams problems when service status pages show no outages but you experience persistent issues, when troubleshooting steps including cache clearing and app reinstallation fail, or when specific features like Teams Calling or file sharing require licensing or permission verification only administrators can access.