by Alex Verboon
The Office 365 solution in Operations Management Suite (OMS) allows you to monitor your Office 365 environment in Log Analytics. Like with any solution that you setup in OMS you have to think of the data retention time. At present the maximum retention time can be set to two years, but this of course will affect your Azure billing. In today’s blog post I walk you through a possible solution how to backup just a Read More …
Here’s a small cmdlet I wrote today to pull the Office 365 roadmap information with PowerShell.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 |
Function Get-Office365Roadmap { <# .Synopsis Get-Office365Roadmap .DESCRIPTION Get-Office365Roadmap retrieves Office 365 information .EXAMPLE Get-Office365Roadmap Retrieves the complete Office 365 roadmap information .EXAMPLE Get-Office365Roadmap -Stats Count Name ----- ---- 203 In development 191 Launched 17 Previously released 61 Rolling out 3 Cancelled .PARAMETER Stats Shows the total number of features grouped by deployment status #> [CmdletBinding()] Param( [switch]$Stats ) Begin{} Process{ $roadmapfeatures = Invoke-WebRequest -Uri https://roadmap-api.azurewebsites.net/api/features $features = $roadmapfeatures.Content $rm = ($features) -join "`n" | ConvertFrom-Json } End{ If ($Stats -eq $true) { $rm | Group-Object Status | Select-Object Count,Name } Else { $rm } } } |
Just recently Microsoft announced the general availability of the Office 365 centralized deployment service. I have tested it and it really makes deploying Office Add-ins super easy. The add-in configuration and deployment can be managed through the Office 365 portal or using PowerShell. For a quick overview watch the video “How to Deploy Office Add-ins within Your Organization”. Now since I like using PowerShell, here’s a quick example how to enable and deploy an Office Read More …
To get a list of all users that belong to a given role, the Microsoft Azure Active Directory module has a cmdlet Get-MsolRoleMember, however to run the cmdlet you must use the RoleObjectId parameter and provide a value. The possible values for RoleObjectId can be retrieved by running the Get-MsolRole cmdlet. To simplify this, I wrote the Get-MsolRoleMemberDetails cmdlet. As you can see from the below screenshot, the list of available roles is dynamically populated. Read More …
A small PowerShell script that lists all users that have the specified Office 365 AccountSkuid enabled on their account.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 |
<# .Synopsis Get-Office365AccountSkuLicensedUsers .DESCRIPTION The Get-Office365AccountSkuLicensedUsers cmdlet retrieves the users that have a specific Office 365 subscription (AccountSkuId) assigned. .EXAMPLE Get-Office365LicenseInfo .PARAMETER AccountSkuId The name of an Office 365 AccountSkuId A list of known AccountSkuId's pre-populated. Extend the list if needed, a list of known AccountSkuIDs can be found here: # http://blogs.technet.com/b/treycarlee/archive/2013/11/01/list-of-powershell-licensing-sku-s-for-office-365.aspx Other usefull sources related to licensing # https://technet.microsoft.com/en-us/library/dn771771.aspx # https://technet.microsoft.com/en-us/library/dn771773.aspx Version 1.1 - added ENTERPRISEWITHSCAL license option #> function Get-Office365AccountSkuLicensedUsers { [CmdletBinding()] [Alias()] Param ( # AccountSkuId [Parameter(Mandatory=$true, ParameterSetName = "AccountSkuId", ValueFromPipelineByPropertyName=$true, Position=0)] [ValidateSet("ENTERPRISEPACK","RIGHTSMANAGEMENT","AAD_PREMIUM","PLANNERSTANDALONE","POWER_BI_STANDARD","ENTERPRISEWITHSCAL")] $AccountSkuId ) Begin { } Process { If ($PSBoundParameters.ContainsKey("AccountSkuId")) { $AccountSkuIdUsers = Get-MsolUser | Select-Object DisplayName,UserPrincipalName -ExpandProperty Licenses | Where-Object {$_.AccountSkuId -like "*$AccountSkuId*"} $AccountSkuIdUsers | Select-Object DisplayName,UserPrincipalName } } End { } } |
When assigning an Office 365 license to a user, by default several service plans are enabled. When assigning an Office 365 E3 license to a user, the following service plans are enabled by default: Azure Rights Management Office 365 Pro Plus Skype for Business Online (Plan 2) Office Online SharePoint Online (Plan 2) Exchange Online (Plan 2) From an end user perspective the user will see the following options when logging on to Office 365. Read More …
On April 28th 2014 Microsoft finally released an fix for the Office 2013 SP1 Office customization tool as the version released with SP1 caused some issues with Lync 2013 and OneDrive for Business. But there’s more in this update.A few new Group Policy settings for Office 365 are included as well. Important. These new Group Policy settings only apply to Office 365 (click to run installations) and not to Office 2013 MSI based installations. The Read More …