Sulich's Blog

Sulich's Blog

Find licensed users in O365 who disabled in Active Directory

http://itinseattle.com/2015/find-disabled-users-licensed-in-office-365/

Office 2013 KMS activation

on the admin elevated cmd:

Manually configuration of KMS host:

C:\Program Files (x86)\Microsoft office\Office15\ cscript ospp.vbs /sethst:hostname

 

Manually activation of Office 2013:

C:\Program Files (x86)\Microsoft office\Office15\ cscript ospp.vbs /act

Accidentally deleted computer from SCCM database

If the computer has been deleted accidentally from the collection or from the database, it can be restored by follow procedures from the client:

  1. Discovery Data Collection Cycle
  2. Hardware Inventory Cycle
  3. Software Inventory Cycle

After few minutes the client will be again into the database

 

SCCM 2012 – Deploying Office 365

https://support.office.com/en-us/article/Deploy-Office-365-ProPlus-with-System-Center-Configuration-Manager-4dd6a023-0a5d-4dc9-9bad-ff70e01840b8?ui=en-US&rs=en-US&ad=US

 

https://support.office.com/en-us/article/Overview-of-the-Office-2016-Deployment-Tool-bb5b62d9-1168-47e9-9d54-15a958acfcca?ui=en-US&rs=en-US&ad=US#bkmk_downloadinstallationfiles

 

 

Win 2012 R2 RDS Powershel cmdlets

Using PowerShell to control RDS in Windows Server 2012 (Part 1)

The Battle of Renaming the RDS Server – 10 Steps of Troubleshooting

 

Problem:

After renaming RDS server , the connection broker and SessionHost remain with old name. Collection pointing to the old server

Resolution:

For resolving  the problem will use Powershell cmdlets

Get-RDServer

 

Get-RDSessionCollection -Connection Broker “Servername”

Remove RD Session Collection

Remove-RDSessionCollection -CollectionName “Collection Name” -ConnectionBroker “ServerName” -Force

Remove RD Server

Remove-RDServer “ServerName” -Role RDS-RD-SERVER -ConnectionBroker “ServerName

Restart the server

Reinstall RDS Broker Role

Remove-WindowsFeature -Name RDS-Connection-Broker

Add-WindowsFeature -Name RDS-Connection-Broker

 

Create new deployment, collection, Session Host and Connection broker:

New-SessionDeployment -ConnectionBroker SERVER.CONTOSO.COM -WebAccessServer SERVER.CONTOSO.COM -SessionHost SERVER.CONTOSO.COM

New-RDSessionCollection -CollectionName SessionCollection -SessionHost SERVER.CONTOSO.COM -CollectionDescription “Session Collection for RDS Server” -ConnectionBroker SERVER.CONTOSO.COM

 

 

Pointing the server to the new license server if needed:

$obj = gwmi -namespace “Root/CIMV2/TerminalServices” Win32_TerminalServiceSetting
$obj.SetSpecifiedLicenseServerList(“SERVER.CONTOSO.COM”)

Check if it is connected to the new license server

$obj = gwmi -namespace “Root/CIMV2/TerminalServices” Win32_TerminalServiceSetting
$obj.GetSpecifiedLicenseServerList()

 

To change the licensing mode on RDSH/RDVH:

$obj = gwmi -namespace “Root/CIMV2/TerminalServices” Win32_TerminalServiceSetting

$obj.ChangeMode(value) – Value can be 2 – per Device, 4 – Per user

 

 

SCCM – create device collection based on the OU

SCCM_WRK_Pilot collection has bean created by query :

sccm_01

 

sccm_02

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.SystemOUName = “contoso.com/Computers/TestGPO”

 

 

SCCM 2012 Device collections based on Operation Systems

Creating SCCM 2012 device colections based on the operation system:

# Variables
$PWDBegin=$PWD
$CMSiteCode=”001″ # Change this – This should be your site code
$CMModule=’D:\Program Files\Microsoft Configuration Manager\AdminConsole\bin\ConfigurationManager.psd1’ # Change this – This should point to the CM module
Import-Module $CMModule
$CMSiteCode = $CMSiteCode+”:”
Set-Location $CMSiteCode
$schedule = New-CMSchedule -RecurInterval Days -RecurCount 7

New-CMDeviceCollection -Name “Windows 8” -LimitingCollectionName “All Systems” -RefreshSchedule $schedule
Add-CMDeviceCollectionQueryMembershipRule -CollectionName “Windows 8” -QueryExpression “select SMS_R_SYSTEM.ResourceName,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueNameentifier, SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.OperatingSystemNameandVersion like ‘%Microsoft Windows NT Workstation 6.2%'” -RuleName “Windows 8”

 

New-CMDeviceCollection -Name “Windows 7” -LimitingCollectionName “All Systems” -RefreshSchedule $schedule
Add-CMDeviceCollectionQueryMembershipRule -CollectionName “Windows 7” -QueryExpression “select SMS_R_SYSTEM.ResourceName,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueNameentifier, SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.OperatingSystemNameandVersion like ‘%Microsoft Windows NT Workstation 6.1%'” -RuleName “Windows 7”

 

New-CMDeviceCollection -Name “Windows Vista”-LimitingCollectionName “All Systems” -RefreshSchedule $schedule
Add-CMDeviceCollectionQueryMembershipRule -CollectionName “Windows Vista” -QueryExpression “select SMS_R_SYSTEM.ResourceName,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueNameentifier, SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.OperatingSystemNameandVersion like ‘%Microsoft Windows NT Workstation 6.0%'” -RuleName “Windows Vista”

New-CMDeviceCollection -Name “Windows XP”-LimitingCollectionName “All Systems” -RefreshSchedule $schedule
Add-CMDeviceCollectionQueryMembershipRule -CollectionName “Windows XP” -QueryExpression “select SMS_R_SYSTEM.ResourceName,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueNameentifier, SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.OperatingSystemNameandVersion like ‘%Microsoft Windows NT Workstation 5.1%'” -RuleName “Windows XP”

New-CMDeviceCollection -Name “Windows Server 2012”-LimitingCollectionName “All Systems” -RefreshSchedule $schedule
Add-CMDeviceCollectionQueryMembershipRule -CollectionName “Windows Server 2012” -QueryExpression “select SMS_R_SYSTEM.ResourceName,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueNameentifier, SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.OperatingSystemNameandVersion like ‘%Microsoft Windows NT Server 6.2%'” -RuleName “Windows Server 2012”

New-CMDeviceCollection -Name “Windows Server 2012 R2” -LimitingCollectionName “All Systems” -RefreshSchedule $schedule
Add-CMDeviceCollectionQueryMembershipRule -CollectionName “Windows Server 2012 R2” -QueryExpression “select SMS_R_SYSTEM.ResourceName,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueNameentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.OperatingSystemNameandVersion like ‘%Microsoft Windows NT Server 6.3%'” -RuleName “Windows Server 2012 R2”

New-CMDeviceCollection -Name “Windows Server 2016” -LimitingCollectionName “All Systems” -RefreshSchedule $schedule
Add-CMDeviceCollectionQueryMembershipRule -CollectionName “Windows Server 2016” -QueryExpression “select SMS_R_SYSTEM.ResourceName,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueNameentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.OperatingSystemNameandVersion like ‘%Microsoft Windows NT Server 10%'” -RuleName “Windows Server 2016”

New-CMDeviceCollection -Name “Windows Server 2008 R2”-LimitingCollectionName “All Systems” -RefreshSchedule $schedule
Add-CMDeviceCollectionQueryMembershipRule -CollectionName “Windows Server 2008 R2” -QueryExpression “select SMS_R_SYSTEM.ResourceName,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueNameentifier, SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.OperatingSystemNameandVersion like ‘%Microsoft Windows NT Server 6.1%'” -RuleName “Windows Server 2008 R2”

New-CMDeviceCollection -Name “Windows Server 2008”-LimitingCollectionName “All Systems” -RefreshSchedule $schedule
Add-CMDeviceCollectionQueryMembershipRule -CollectionName “Windows Server 2008” -QueryExpression “select SMS_R_SYSTEM.ResourceName,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueNameentifier, SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.OperatingSystemNameandVersion like ‘%Microsoft Windows NT Server 6.0%'” -RuleName “Windows Server 2008”

New-CMDeviceCollection -Name “Windows Server 2003”-LimitingCollectionName “All Systems” -RefreshSchedule $schedule
Add-CMDeviceCollectionQueryMembershipRule -CollectionName “Windows Server 2003” -QueryExpression “select SMS_R_SYSTEM.ResourceName,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueNameentifier, SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.OperatingSystemNameandVersion like ‘%Microsoft Windows NT Server 5.2%'” -RuleName “Windows Server 2003”
Set-Location $PWDBegin

 

AD FS Troubleshooting

https://support.microsoft.com/en-ca/help/3015526/how-to-troubleshoot-issues-that-you-encounter-when-you-sign-in-to-offi

 

How to troubleshoot issues that you encounter when you sign in to Office apps for Mac, iPad, iPhone, or iPod Touch when using Active Directory Federation Services

INTRODUCTION

This article contains information about how to troubleshoot problems that affect the ability to sign in to Microsoft Office apps for Mac, iPad, iPhone, or iPod Touch. This article also contains resources for IT administrators to address reports about Active Directory Federation Services (AD FS) issues that are specific to Office for Apple iOS and Mac platforms.

Issue Recommendation
Issue 1: “Unknown Auth method” message when you try to sign in to an Office app for iOS or Mac To resolve this issue, your administrator must contact the provider of your non-Microsoft federation server to verify the configuration.
Issue 2: “An error occurred. Contact your administrator” message when you try to sign in to an Office app for iOS or Mac To resolve this issue, contact your administrator and point to this article.
Issue 3: “An error has occurred, invalid SAML token” error message when you try to sign in to an Office app for iOS or Mac To resolve this issue, contact your administrator and point to this article.
Issue 4: “There is problem with your account, please try again later“ error message when you try to sign in to an Office app for iOS or Mac Users can update to the latest version of the Mac or iOS apps that are available. If this does not resolve the issue, contact your administrator and point to this article.
Issue 5: The sign-in page continually reappears when you try to sign in to any of the Office 365 apps for iOS or Mac To resolve this issue, contact your administrator and point to this article.

MORE INFORMATION

Issue 1: “Unknown Auth method” message when you try to sign in to an Office app for iOS or Mac

This error can occur in a topology where an enterprise has federated an AD FS server with Azure Active Directory for signing in to Office 365, and further federated the AD FS server with another non-Microsoft federation server such as Shibboleth. When Mac and iOS Office applications sign in, Azure Active Directory sends a parameter in the sign-in request to AD FS that requests forms authentication. When AD FS relays this request to the non-Microsoft federation server, it may be unable to interpret this parameter and it may display an error to the user, even before they are asked to sign in.

To resolve this issue, contact the provider of your non-Microsoft federation server.

Issue 2: “An error occurred. Contact your administrator” message when you try to sign in to an Office app for iOS or Mac

Users can’t sign in if the tenant uses AD FS and forms-based authentication is turned off on the AD FS server. They receive the following error message:

An error occurred

An error occurred. Contact your administrator for more information.

Error details

  • Activity ID: 00000000-0000-0000-c32d-00800000005e
  • Relying party: Microsoft Office 365 Identity Platform
  • Error time: <Date> <Time>
  • Cookie: enabled
  • User agent string: Mozilla/5.0 (Windows NT 6.3;WOW64)
    AppleWebKit/537.36 (KHTML, like Gecko)
    Chrome/38.0.2125.111 Safari/537.36

In certain AD FS configurations, the administrator may not have forms-based authentication enabled on the AD FS server. This prevents Mac clients from logging in as required by the authentication process.

To resolve this issue, set up AD FS to use forms-based authentication as the secondary form of authentication. To do this, follow the appropriate steps for the version that you use.

Note The currently configured authentication methods can remain unchanged. For example, if Windows Integrated Authentication is configured as the primary authentication method, it can remain configured this way.

If you use AD FS 2.0

Enable forms-based authentication by using the steps in the following Microsoft TechNet topic:

If you use AD FS in Windows Server 2012 R2

Follow these steps:

  1. In Server Manager on the AD FS 3.0 server, click Tools, and then select AD FS Management.
  2. In the AD FS snap-in, click Authentication Policies.
  3. In the Primary Authentication section, click Edit next to Global Settings.
  4. In the Edit Global Authentication Policy dialog box, click the Primary tab, and then under Extranet and under Intranet, click to select the Forms Authentication check box.Screen shot of the Edit Global Authentication Policy dialog box, showing the Forms Authentication check boxes

Issue 3: “An error has occurred, invalid SAML token” error message when you try to sign in to an Office app for iOS or Mac

When you try to sign in, you receive the following error message:

An error has occurred, invalid SAML token.

The complete error may resemble the following:

We received a bad request.
Additional technical information:
Correlation ID: 82121251-3634-4afb-8014-fb5298d6f2c9
Timestamp: 2014-11-01 00:25:35Z
AADSTS50008: SAML token is invalid

This is a known Azure Active Directory issue. A fix is expected to become available soon. In the meantime, you can run the following Windows PowerShell script to resolve the issue.

Note You must run the PowerShell script one time for each affected federated domain.

  1. Make sure that you have the latest Azure Active Directory Module for Windows PowerShell. For more information, go to the following Microsoft Office website:
  2. Run the following command in PowerShell on the AD FS server:
    Update-MsolFederatedDomain -DomainName [verified domain]

Issue 4: “There is problem with your account, please try again later“ error message when you try to sign in to an Office app for iOS or Mac

Administrators who have configured AD FS 2012 R2 to let users sign in by using an alternative user identifier, such as their email address, may experience this error. Users typically sign in by using their user principal name (UPN). We are working on an update to the Mac and iOS applications to support signing in by using an alternative user identifier.

To resolve this issue, update to the latest version of Mac and iOS apps. Verify the configuration of AD FS 2012 R2 to let users sign in by using an alternative user identifier.

Issue 5: The sign-in page continually reappears when you try to sign in to any of the Office 365 apps for iOS or Mac

Important Because of a temporary mitigation in Azure Active Directory, some users who have successfully signed in between October 30, 2014 and December 2, 2014 may start experiencing this issue after December 2, 2014. Make sure that the update that’s mentioned in this section is installed.

When a user signs in to any of the Office 365 apps for iOS or Mac, the user enters their user name and password on the sign-in page and the sign-in page reappears and prompts the user for their user name and password again. This problem can occur if you’re using an AD FS 2.0 server that’s missing critical updates. Install the update that’s documented in the following Microsoft Knowledge Base article on the AD FS 2.0 server:

2989956 Several issues after you install security update 2843638 or 2843639 on an AD FS server

Cool script for getting all individual license plans for all licensed users in Office 365

https://community.spiceworks.com/scripts/show/3698-report-on-office-365-user-license-assignment-with-powershell

by

Description

Get-O365UserLicenseReport is a Windows PowerShell function that outputs Office 365 user license assignments, including individual service plans, that can be easily viewed or exported to file.

function Get-O365UserLicenseReport
{
<#
.SYNOPSIS
Generates a report of Office 365 license assignments
.DESCRIPTION
Generates a report of Office 365 license assignments by license sku, including individual service plan assignments.

This command requires that you have a global administrator account for an Office 365 tenant and can connect to Office 365 using
Windows PowerShell. Instructions for this can be found at http://powershell.office.com/.

.PARAMETER MsolUser
The Office 365 user account(s) that you’d like to report on.

.PARAMETER AccountSkuId
The name of the license sku you’d like to report on. These can be found by running the command:

Get-MsolAccountSkuId

.PARAMETER UserProperties
Optional. Any Office 365 user properties that you’d like to include in the report. These could help you determine a user’s role to aid in finding
where license assignments are incorrect. For instance, if your users are provided certain license assignments based on their department
you may want to include the “Department” property in the resulting report for comparison.

Acceptable values are:

City
Country
Department
FirstName
LastName
Office
PhoneNumber
PostalCode
State
StreetAddress
Title
UsageLocation

The DisplayName and UserPrincipalName will always be included, regardless of properties specified by the UserProperties parameter.

.EXAMPLE
$Credential = Get-Credential
Connect-MsolService -Credential $Credential
Get-MsolUser -All | Where IsLicensed -eq $true |
Get-O365UserLicenseReport -AccountSkuId whitehouse:Enterprisepack -UserProperties Department,Office

This example will return information for all your Office 365 users who are assigned at least one service plan in the EnterprisePack
license sku. It starts by saving a credential object in the $Credential variable. Next you collect all your Office 365 users with at
least one license and pass those down the pipeline to the Get-O365UserLicenseReport command.

.EXAMPLE
Get-MsolUser -All | Where IsLicensed -eq $true |
Get-O365UserLicenseReport -AccountSkuId whitehouse:Enterprisepack -UserProperties Department,Office |
Export-Csv c:\Reports\EnterprisePack.csv -NoTypeInformation

This example, like the previous one, will collect license information for all your users, but this time will export it to a csv file for
posterity.

.EXAMPLE
$Skus = Get-MsolAccountSku | Where-Object { $_.ConsumedUnits -ge 1 }
$Users = Get-MsolUser -All | Where-Object { $_.IsLicensed -eq $true }

foreach ($Sku in $Skus)
{
Get-O365UserLicenseReport -MsolUser $Users -AccountSkuId $Sku.AccountSkuId -UserProperties Department,Office |
Export-Csv “c:\Reports\$($Sku.SkuPartNumber).csv” -NoTypeInformation
}

This example is what I call the nuclear option – it will collect information for all your license skus that have at least one assigned
user and output a report for each in CSV format. These will be saved to the folder location “c:\Reports” and each file name will be match
the sku name.
#>

[CmdletBinding()]
param
(
[Parameter(Mandatory = $true, ValueFromPipeline = $true)]
[Microsoft.Online.Administration.User[]]
$MsolUser,

[Parameter(Mandatory = $true)]
[string]
$AccountSkuId,

[Parameter(Mandatory = $false)]
[ValidateSet(
“City”,
“Country”,
“Department”,
“FirstName”,
“LastName”,
“Office”,
“PhoneNumber”,
“PostalCode”,
“State”,
“StreetAddress”,
“Title”,
“UsageLocation”
)]
[string[]]
$UserProperties
)

process
{
foreach ($User in $MsolUser)
{
$License = $User.Licenses | Where-Object { $_.AccountSkuId -eq $AccountSkuId }

if ($License)
{
$Properties = [Ordered]@{
DisplayName = $User.DisplayName
UserPrincipalName = $User.UserPrincipalName
}

foreach ($Property in $UserProperties)
{
$Properties.Add($Property, $User.$Property)
}

foreach ($Plan in $License.ServiceStatus)
{
$Properties.Add($Plan.ServicePlan.ServiceName, $Plan.ProvisioningStatus)
}

New-Object -TypeName PSCustomObject -Property $Properties
}
}
}
}

Example for use :

$Skus = Get-MsolAccountSku | Where-Object { $_.ConsumedUnits -ge 1 }
$Users = Get-MsolUser -All | Where-Object { $_.IsLicensed -eq $true }

foreach ($Sku in $Skus)
{
Get-O365UserLicenseReport -MsolUser $Users -AccountSkuId $Sku.AccountSkuId -UserProperties Department,Office |
Export-Csv “c:\Reports\$($Sku.SkuPartNumber).csv” -NoTypeInformation
}

Office 365 licenses and Service Plans

Licenses E3

#All licensed users list

Get-MsolUser –All | Where-Object { $_.isLicensed -eq “TRUE” } | Select-Object UserPrincipalName, DisplayName, Department | Export-Csv c:\Scripts\LicensedUsers.csv

#the list of users without license

get-mailbox | where {($_.recipienttypedetails -ne “Discoverymailbox”) -and ($_.skuassigned -ne “True”)} | ft name,skuassign*

#E3 license – Set Canada location for the user and disabling all products except MCOSTANDARD (Skype for business Online Plan 2) and EXCHANGE_S_ENTERPRISE (Exchange Online Plan 2). Please change your “username@email.com” and tenant:ENTERPRISEPACK information

$strMoveRequestPrimaryEmailAddress = “username@email.com”

Set-MsolUser -UserPrincipalName $strMoveRequestPrimaryEmailAddress -UsageLocation CA

Set-MsolUserLicense -UserPrincipalName $strMoveRequestPrimaryEmailAddress -AddLicenses tenant:ENTERPRISEPACK

$O365Sku = New-MsolLicenseOptions -AccountSkuId tenant:ENTERPRISEPACK -DisabledPlans FORMS_PLAN_E3,STREAM_O365_E3,Deskless,FLOW_O365_P2,POWERAPPS_O365_P2,TEAMS1,PROJECTWORKMANAGEMENT,SWAY,INTUNE_O365,YAMMER_ENTERPRISE,RMS_S_ENTERPRISE,OFFICESUBSCRIPTION,SHAREPOINTWAC,SHAREPOINTENTERPRISE

Set-MsolUserLicense -UserPrincipalName “$strMoveRequestPrimaryEmailAddress” -LicenseOptions $O365Sku

List of users who has some specific Plan:

$plan = “SHAREPOINTSTANDARD”

$sku = (Get-MsolAccountSku) | ? {$_.ServiceStatus.ServicePlan.ServiceName -eq $plan}

$index = ($sku).ServiceStatus.ServicePlan.ServiceName.IndexOf($plan)

Get-MsolUser -All | ? { ($_.Licenses) -and ($_.Licenses[-1].ServiceStatus[$index].Provisioningstatus -eq “Success”) -and ($_.Licenses.AccountSkuId -eq $sku.AccountSkuId)}

#List of all service plans for license

Get-MsolAccountSku | Select -ExpandProperty ServiceStatus

#List of all licenses

Get-MsolAccountSku

#List of all service plans for specific user

$strMoveRequestPrimaryEmailAddress = “username@email.com”

(Get-MsolUser -UserPrincipalName $strMoveRequestPrimaryEmailAddress ).Licenses.ServiceStatus

E3 Service Plans

Microsoft Forms (Plan E3) FORMS_PLAN_E3
Stream for Office 365 STREAM_O365_E3
Microsoft StaffHub Deskless
Flow for Office 365 FLOW_O365_P2
PowerApps for Office 365 POWERAPPS_O365_P2
Microsoft Teams TEAMS1
Microsoft Planner PROJECTWORKMANAGEMENT
Sway SWAY
Mobile Device Management for Office 365 INTUNE_O365
Yammer Enterprise YAMMER_ENTERPRISE
Azure Rights Management RMS_S_ENTERPRISE
Office 365 ProPlus OFFICESUBSCRIPTION
Skype for Business Online (Plan 2) MCOSTANDARD
Office Online (can’t be assigned without Sharepoint Online) SHAREPOINTWAC
SharePoint Online (Plan 2) (include Onedrive) SHAREPOINTENTERPRISE
Exchange Online (Plan 2) EXCHANGE_S_ENTERPRISE

E1 Service Plans

Microsoft Forms (Plan E1) FORMS_PLAN_E1
Stream for Office 365 STREAM_O365_E1
Microsoft StaffHub Deskless
Flow for Office 365 FLOW_O365_P1
PowerApps for Office 365 POWERAPPS_O365_P1
Microsoft Teams TEAMS1
Office Online (can’t be assigned without Sharepoint Online) SHAREPOINTWAC
Microsoft Planner PROJECTWORKMANAGEMENT
Sway SWAY
Mobile Device Management for Office 365 INTUNE_O365
Yammer Enterprise YAMMER_ENTERPRISE
Skype for Business Online (Plan 2) MCOSTANDARD
SharePoint Online (Plan 1) (include Onedrive) SHAREPOINTSTANDARD
Exchange Online (Plan 1) EXCHANGE_S_STANDARD

 

Post Navigation