Article Table of content | Click to Expand

PowerShell | Help & additional information

Running PowerShell commands in Office 365 based environment To be able to run the PowerShell commands specified in the current article, you will need to create a remote PowerShell with Azure Active Directory or Exchange Online. In case that you need help with the process of creating a Remote PowerShell session, you can use the links on the bottom of the Article.

Resource Mailbox is a special type or a Mailbox that uses for the management of Meeting Rooms and Equipment. The Resource Mailbox doesn’t require a license. Management of Resource Mailbox could implement by using one of the following options:

Resource Mailbox Delegate – The delegate is the person that will accept the meeting requests and approve or decline the meeting requests.

The term “resource Mailbox” includes two types of Mailboxes – Room Mailbox and Equipment Mailbox.

There is a small difference between the two types of the resource mailbox but the use, and the purpose is quite similar (most of the examples will relate to room Mailbox).

A little confession – I must admit that it wasn’t easy to give up the strong need for naming these articles: Get a Room! (But I know that this is a “serious” WebSite and, for this reason, I use a formal name).

Creating a remote PowerShell session to Azure Active Directory To get more information about the required software component + the remote PowerShell commands that you need to use for connecting Azure Active Directory, read the following article: Part 2: Connect to Office 365 by using Remote PowerShell

Basic introduction to PowerShell in Office 365 based environment If you are new in the PowerShell world, you can read more information about how to start working with PowerShell in Office 365 based environment in the following article series: Getting started with Office 365 PowerShell – Part 1, Part 2, Part 3.

Running and using o365info PowerShell scripts In case that you need more information about how to use the o365info PowerShell scripts that I add to the PowerShell articles, you can read the article – How to run and use o365info PowerShell menu script

PowerShell command syntax – Office 365 | Article series index

Now it’s Your Turn! It is important for us to know your opinion on this article

Please rate this

Sample rating item

Summary

Article Name

Manage Room Mailbox by using PowerShell | Office 365

Description

In the current article, we will review how to use PowerShell commands for managing Room mailbox in Exchange Online environment.

24 Comments

We create a Security Group and assign that group to be the resource Delegate, this allows the group owner to select the delegates. The group has “FullAccess” to the resource; the group has “Reviewer” access to the /Calendar:Add-MailboxPermission -Identity Resource_Name -AccessRights FullAccess -User Security_Group

The use of security groups gives greater flexibility for resource management. For some resources, our default of “Reviewer” may be insufficient; the delegates may change this via Outlook (or contact us).

As far as I know , the issue of “converting an existing Distribution Group to a security group” is not enabled in office 365 ( Exchange online)The only option to set Distribution Group also as a “Security Group” is when you create a new Distribution Group. To set a Distribution Group also as a security group you can use one of the following options: 1. Exchange online Web Interface when you create a new Distribution Group chooses the check box: “Make this group a security group”2. PowerShell For example: New-DistributionGroup -Name “Office Users” -Type “Security”If you want to be sure that this option is not enabled, you can try to use the following PowerShell commandSet-DistributionGroup -name “Office Users” -Type “Security”You will get the following error “A parameter cannot be found that matches parameter name ‘Type’”

Give me error “Error term ‘Add-RecipientPermission’ is not recognized as the name of a cmdlet, function, script file, or operable progra heck the spelling of the name, or if a path was included, verify that the path is correct and try again.”

The Room can be renamed and the bookings will stay in place, but the organizers calendar will not update nor will attendee calendars be updated, so you need to warn the organizer that the room is renamed, then he must update the room in his invite and send it to the attndees. Pretty Painful.

You can rename the room, and the bookings will remain in place in the room calendar, but the new name is NOT reflected in the organizers calendar nor the Attendee calendar. So you must manually warn the organizer that the change has occurred and that they should update the room name in the booking and send the update a to the attendees.

I am reviewing the output of me current resource rooms to the ones I just created and I am finding that I am not able to add the group while in the GUI, thus the reason I am here collecting PS commands. However what I am finding is that I need to change several additional areas:

I am looking at locking down some resource calendars such that only 1 of our 365 domains can book it. Can i do this without maintaining a security group for all users of that particular domain? I want just some rooms to be bookable by one domain, others by everyone. All domains are in our 365 tenant of course.