With all the hype with video chat and the customization of Teams now I figured a quick blog post of the “How-To” would be cool.
There are two ways you can do this, the first way is if the option has not made it out to your tenant yet. Get your custom picture and upload to %APPDATA%\Microsoft\Teams\Backgrounds then you can create a meet now to test.
Meet now can simply be created by going to the calendar tab –> Meet now in the top right
Once that is done you can click on the 3 … (More Action) Select “show Background effects” In the list you should see you custom background. Select it and you are all set.
Now, If your tenant has the latest update you can do the same as above but simply upload your custom background by selecting the “Upload Image” button.
Before we proceed to this
section make sure your directory data has values that you can use to
define segments. List of attributes you can use with information barriers
can be found here:
First run
Get-informationbarrierpolicy to see a list of our policies we defined:
In this example the
Guid from running the above cmdlet is 15912fe7-0dd5-4b90-b3e0-4b94168cb63e so
we will run:
Set-InformationBarrierPolicy
-Identity 15912fe7-0dd5-4b90-b3e0-4b94168cb63e -State Active
Then you must also
run this same cmdlet for the other segment we created using its guid.
Now that we have
defined our two segments you must run
the following cmdlet to “start” the policy:
Start-InformationBarrierPoliciesApplication
At this point you should be all setup.
However, After approximately a half hour, policies are applied, user by
user, for your organization. If your organization is large, it can take 24
hours (or more) for this process to complete. (As a general guideline, it takes
about an hour to process 5,000 user accounts.)
At times we have users that create channels leave the org and we end up with a rouge channel. When this happens we need to assign ownership to a new user. This blog will quickly touch on that and hopefully give some guidance on how to do so.
We will go through creating a private room then disable the creator in AD.
First we login and build a team from scratch
Once the channel has been created we add a few users to the room.
After this we disable the owner in AD
Wait for AD replication and then try to sign in as the current owner
As you can see this user is no longer valid in AD but they are still considered the owner of the channel
To fix this simply go into your Teams admin center select Teams –> Manage Teams –> select the Team you want to edit –> then select the user that will be the new owner. This should then take care of a rouge user being an owner of the channel in question.
This blog will touch on share mailboxes for resource accounts including Call Queues and Auto Attendants.
In the Exchange online admin portal go to recipients –> groups ->create group
Fill out all the information that you need; the below information would be needed as well. Also you will need to add the members to the group.
3. Once this is completed you can go under your Auto Attendant in the Teams GUI and configure as needed.
This should give you the shared mailbox option now for your Auto Attendant. I have not tested this in great detail. Feedback would be appreciated on this one.
Currently have had a few calls where there have been a few issues adding phone numbers to resource accounts for Auto Attendant. This is just a quick guide that might be of some use.
Pre reqs if you will.
Purchase the virtual licenses for Virtual user – Sign into the M365 admin center – Go to Billing –> Purchase Services –> Add-on subscriptions – Scroll to the end to find the “Phone System-Virtual User” license. Select “buy Now” this is a free license.
Make sure you have the service numbers ready to assign to your resource account. – Admin center –> Teams –> Voice –> Phone numbers –> add –> fill in the necessary information.
Now that we have the licensing and numbers in place we need to create the resource account. The official documentation for this can be found here . My lab is hybrid so I have to first go to the 2019 Skype powershell and run the following cmdlet:
You can either wait for ADD to sync or you can force it using this cmdlet:
Start-ADSyncSyncCycle -PolicyType Delta
Once AD has synced and you can see your user in the list in the “Active user” list go ahead and assign the license we gathered in step 1. “Phone System-Virtual User”
Once the user has the license now its time to configure your Auto Attendant.
Teams portal –> Voice –> Auto Attendants –> Add
Fill in all the information as needed. Dont worry about the phone number yet just complete the wizard and assign your resource account.
Now once you have completed this you can go under your resource account found under Org-Wide Settings –> Resource accounts –> Newly created account –> Assign/Unassign.
At this point we have setup the resource account, AA and assigned the number. You should be able to call the number and test to verify that AA is indeed working.
In a future blog I will introduce Call queue and Shared voicemail