Microsoft Teams quick start in the organizational structure of the series -07Teams

Previous article describes how to communicate with external organizations Teams. But not inevitably cross-organizational collaboration in their daily work, such as: XX project, by Party A and Party B Teams will be added to a Teams which make the project more smoothly. Here to share with you how to organize external users to join an existing team.

There will be a thing of the organizational structure in various systems within the enterprise self-built in, which contains a sub-distribution company departments and personnel, end users can be found throughout the company organizational structure according to any one user. In Office365 then there is no such similar things? The answer is yes, the global version Office365 Teams in the provision of internal organization chart. Let's look at renderings (The following are the display Demo content) :

image.png

image.png

image.png

The feeling is not it cool? Is not it easier to find someone up? Man card information as layered cards, can be very intuitive to see what the current position is that the user belongs to which department, but also can be a key to initiate IM audio and video communication, or send an e-mail.

Often there will be such a large enterprise application scenarios, A a small departmental staff a project may require a small b B sector to provide technical support, but the entire staff has thousands of employees, and a small basic B sector do not know, this time small a need to need to get a small b's technical support informed of their department heads and B department heads and small b by mail, you can easily find leading B sector through Teams of the organization chart and small b.

To demonstrate the formation of this organization, Office365 background administrator needs to improve relations manager for each user (in fact, this thing is AD user properties manager, although most companies are not going to maintain this information in a local deployment). There are two ways finishing:

First: Azure AD found in the user attribute, the attribute information editing manager can achieve this effect. This applies to small organizations only a few dozen users

Second: By setting in PowerShell batch, you can achieve the same effect. For medium to large enterprises if the organizational structure is more complex or more persons recommended when using this method.

The following describes the two methods, graphical interface operates as follows:

首先需要登录在office365管理中心,进入Azure AD

image.png

然后点击用户,搜索需要添加经理的用户image.png

在作业信息中点击编辑image.png

填写好经理关系(部门职务等也可以在这里维护),并点击保存image.png

这样就设置完成了。

那么如果要批量进行设置呢,首先我搜索了Set-Msoluser命令发现,并不能在Azure AD PowerShell中直接去设置用户的manager属性。Set-MsolUser参考链接如下:

https://docs.microsoft.com/en-us/powershell/module/msonline/set-msoluser?view=azureadps-1.0

可以看到并没有Manager属性,那么我们就不能使用Set-MsolUser命令来进行批量设置了。

image.png

但是办法总归是有的,细心的同学可能会发现在Exchange 用户属性中也是是有经理属性的(由此可以发现图形化界面不仅仅可以在Azure AD中操作,也可以在Exchange管理中心操作),那么我们能不能用Exchange的PowerShell来进行设置呢?image.png

我试了下连到Exchange Online PowerShell去设置是生效的,那么我们需要批量设置的话,就需要创建一个CSV文件,来对应用户和相应的经理是谁了image.png

然后使用Powershelll连到Exchage Online 具体怎么连接可以参考Exchange Online基于网络位置限制使用中的描述image.png

然后切换目录到存放CSV的位置,并使用以下命令进行设置

Import-CSV <nameofcsv>.csv|%{Set-User $_.Identity -Manager $_.Manager}image.png

完成后查看打杂小弟B的属性,发现经理已经出现image.png

这样就完成了整个设置。

CSV文件中可以包含整个组织的所有用户和经理关系,不需要一个部门一个csv文件去维护。


Guess you like

Origin blog.51cto.com/scnbwy/2407640
Recommended