Error Details
| Fact | Value | Source | Note |
|---|
| Exact error string | Error code: 30015-26 | Office licensing log | -> indicates missing licence |
| Affected build range | Microsoft 365 Apps for Enterprise / Business | | |
| Registry key or OMA-URI involved | HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Office\16.0\Licensing | Registry Editor | -> check for policy overrides |
| Relevant service/endpoint URL | activation.sls.microsoft.com | | -> required for Shared Computer Activation (SCA) |
| Log line signature | <Event xmlns='http://schemas.microsoft.com/win/2004/08/events/event'><System><Provider Name='Microsoft Office'/></System><EventData><Data Name='ErrorCode'>30015-26</Data></EventData></Event> | Windows Application event log | |
Log Files to Check
C:\Users\<user>\AppData\Local\Microsoft\Office\16.0\Licensing\ospp_licensing.logC:\Program Files\Microsoft Office\root\Office16\OSPPREARM.EXE
What This Error Actually Means
The error code 30015-26 is a licensing issue that occurs when Microsoft 365 Apps for Enterprise or Business cannot validate the license assigned to the user account. This error typically arises due to issues with Azure Active Directory (AAD) licensing configurations, network connectivity problems, or misconfigurations in conditional access policies. The component responsible for raising this error is primarily the Office Licensing Service, which checks the validity and assignment of licenses during activation.
Affected Versions and Scope
This error affects Microsoft 365 Apps for Enterprise and Business, specifically targeting builds that require a valid license to activate. It does not impact users with personal or free subscriptions like Microsoft 365 F1/F3 plans which do not include desktop Office applications. The issue is scoped to environments where Azure AD/Entra ID manages licensing assignments and synchronization.
Where To Look First: Logs and Event IDs
To diagnose this error, you need to inspect several log files and event logs:
- **Office Licensing Log**: Located at
C:\Users\\AppData\Local\Microsoft\Office\16.0\Licensing\ospp_licensing.log. This file contains detailed XML entries about the last license check result, including error codes.
- **Windows Application Event Log**: Navigate to
Event Viewer > Windows Logs > Application, and look for events sourced from 'Microsoft Office' with an event ID of 30015 or a description containing 'LicensingFailure'. The exact log line signature is:
```xml
30015-26
```
- **Office Activation Troubleshooter Output**: Run the command
cscript ospp.vbs /dstatus in the folder
C:\Program Files\Microsoft Office\root\Office16. This will provide information about the current license state.
Root Causes
There are several root causes for this error:
- **Missing or Revoked License**: The user account lacks a valid Microsoft 365 Apps license in Azure AD/Entra ID. To confirm, navigate to
Microsoft 365 admin center > Users > Active users > select user > Licenses and apps. If the required SKU is missing, this indicates an unassigned or revoked license.
- **Network Connectivity Issues**: Shared devices using Shared Computer Activation (SCA) may encounter network issues preventing them from reaching the Office licensing service endpoint at
activation.sls.microsoft.com. Check firewall rules and ensure that outbound traffic on port 443 is allowed for this domain.
- **Conditional Access Policy Blocking Licensing Service Requests**: Conditional access policies might be configured to block OAuth requests for the licensing service. Review policies in
Azure AD admin center > Users > Active users > select user > Licenses and apps or check Azure AD sign-in logs filtered by 'Office 365' application.
- **Incompatible License Plan**: If a Microsoft 365 F1/F3 plan is assigned, which does not include desktop Office applications, this will result in the error. Ensure that users are assigned an appropriate license SKU for their needs.
Fix Procedure
To resolve the issue, follow these steps:
- Assign or Reassign Licenses: Navigate to
Microsoft 365 admin center > Users > Active users > select user > Licenses and apps. Assign a valid Microsoft 365 Apps license SKU.
- Check Network Connectivity: Ensure that the device can reach
activation.sls.microsoft.com. Use tools like ping activation.sls.microsoft.com or nslookup activation.sls.microsoft.com.
- Review Conditional Access Policies: Navigate to
Azure AD admin center > Users > Active users > select user > Licenses and apps. Review conditional access policies for any rules that might block OAuth requests.
- Modify Registry Key (Optional): If the issue persists, modify the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Office\16.0\Licensing to adjust licensing behavior. Be cautious as incorrect modifications can break enrolled devices.
- Run PowerShell Commands: Use the following PowerShell cmdlets to check and modify license assignments:
Running these commands incorrectly could affect device management policies.
```powershell
Get-MgDeviceManagementManagedDevice -Filter "deviceEnrollmentType eq 'windowsAutoEnrollment'"
Invoke-MgGraphRequest -Method GET -Uri "https://graph.microsoft.com/v1.0/deviceManagement/managedDevices"
```
Error Code Variants
| Code |
Description |
Distinguishing Feature |
30015-26 |
Licensing failure due to missing or revoked license. |
User has no assigned Microsoft 365 Apps license in Azure AD/Entra ID. |
30015-27 |
Licensing failure due to network connectivity issues. |
Error occurs on shared devices using SCA and unable to reach licensing service endpoint. |
30015-28 |
Licensing failure due to conditional access policy blocking OAuth requests. |
Error appears when OAuth requests are blocked by a conditional access policy. |
Verification
To verify that the issue is resolved:
- Check the Office licensing log at
C:\Users\\AppData\Local\Microsoft\Office\16.0\Licensing\ospp_licensing.log. Look for entries indicating successful license validation.
- Run
cscript ospp.vbs /dstatus in the folder
C:\Program Files\Microsoft Office\root\Office16 and confirm that the license state is valid.
- Use PowerShell cmdlets to verify device management policies:
```powershell
Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" -MaxEvents 50
```
Prevention
To prevent recurrence of this error:
- Ensure that all users are assigned the correct Microsoft 365 Apps license SKU in Azure AD/Entra ID.
- Regularly review and update conditional access policies to avoid blocking necessary OAuth requests for licensing services.
- Implement network monitoring tools to detect connectivity issues with
activation.sls.microsoft.com.
A quick diagnostic shortcut is to use the command dsregcmd /status to check Azure AD registration status and verify if the device can connect to licensing services.
By following these steps, you should be able to diagnose and resolve error code 30015-26 effectively in Microsoft 365 Apps environments.