新的User.employeeId ExtensionProperty无法正常工作 [英] New User.employeeId ExtensionProperty not working

查看:53
本文介绍了新的User.employeeId ExtensionProperty无法正常工作的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

最近在我们的租户中,user实体出现了一个新的employeeId属性.

Recently in our tenant appeared a new employeeId attribute to the user entity.

我们有超过4万个用户帐户;其中一些创建为纯Azure AD用户,其他创建为邮件用户(通过Exchange Online).

We have over 40k user accounts; some of them created as pure Azure AD Users and others as Mail Users (via Exchange Online).

对于许多帐户,尝试POSTemployeeId失败,并显示以下错误:

For many accounts, attempting to POST to the employeeId fails with the following error:

无法为源自外部服务的对象更新指定的属性.

Unable to update the specified properties for objects that have originated within an external service.

我们已经尝试通过Microsoft Graph(/Beta),Azure Graph API(v1.6)以及通过AAD v2 PowerShell模块进行尝试.

We have tried with Microsoft Graph (/Beta), Azure Graph API (v1.6) and via the AAD v2 PowerShell module.

推荐答案

此用户是否正在从本地同步(使用AD Connect)?如果是这样,则用户的大多数属性都将在本地AD中掌握,并且无法在云中更改/更新.您需要在本地AD中更新此属性(它将同步).

Is this user being synchronized from on-premises (using AD Connect)? If so then most of the properties for the user are mastered in on-premises AD and cannot be changed/updated in the cloud. You need to update this property in the on-premises AD (and it'll sync).

更新:抱歉,回复晚.问题是,对于通过Exchange创建的仅云用户(例如Exchange PowerShell),意味着这些用户被标记"为Exchange创建的用户.对于某些属性,例如employeeId,这可能意味着该特定属性只能由创建服务(Exchange)进行更新.这对于Exchange提供的电子邮件地址和代理地址是有意义的,并且是Exchange的所有者,但对于employeeId则没有意义.

UPDATE: Sorry for the late response. The issue was that for cloud-only users that were created through Exchange (like Exchange PowerShell) meant that these users are "marked" as created by Exchange. For some properties, like employeeId, this can mean that that particular property can only be updated by the creating service (Exchange). This makes sense for things like email addresses and proxyaddresses that Exchange provides and is the owner for - but doesn't make sense for employeeId.

我认为此问题已已解决,并且已推广到生产环境.我已经可以通过以下方式对此进行初步验证:

I believe this issue is now fixed and it has been rolled out to Production. I have been able to do a rudimentary validation for this by:

  1. 使用Exchange PowerShell创建云用户,并且
  2. 使用Microsoft Graph预览/beta端点中的PATCH操作更新新创建的云用户的employeeId.现在,此步骤成功了(而不是抛出错误)
  1. Creating a cloud-user using Exchange PowerShell, and
  2. Updating the newly created cloud-user's employeeId, using a PATCH operation in Microsoft Graph preview /beta endpoint. This step is now successful (rather than throwing an error)

如果您的情况现在已解决,请告诉我们.

Please let us know if this is now fixed for your scenarios.

希望这会有所帮助,

这篇关于新的User.employeeId ExtensionProperty无法正常工作的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆