starred/Set-OutlookSignatures-Set-OutlookSignatures

Fork 0

mirror of https://github.com/Set-OutlookSignatures/Set-OutlookSignatures.git synced 2026-04-26 10:45:52 +03:00

[GH-ISSUE #130] Shared mailboxes are not found via Graph, signatures can not be applied #56

New issue

Closed

opened 2026-02-27 20:31:01 +03:00 by kerem · 3 comments

kerem commented

2026-02-27 20:31:01 +03:00

Owner

Originally created by @GruberMarkus on GitHub (Nov 21, 2024).
Original GitHub issue: https://github.com/Set-OutlookSignatures/Set-OutlookSignatures/issues/130

Issue happens in the latest release

I confirm that the issue happens in the latest release of Set-OutlookSignatures

Previously solved issues and documentation

I have searched through issues, discussions and documentation, but have not found an answer to my issue

Code of Conduct

I agree to follow this project's Code of Conduct

What happened?

Shared mailboxes are not found in Entra ID via Graph queries, although they exist.

Set-OutlookSignatures shows the following output:

Get properties of each mailbox @2024-11-21T14:04:05+01:00@
[...]
  SharedMailbox@example.com
    Search for mailbox user object in Graph:     No matching mailbox object found via Graph/Entra ID. Use parameter '-verbose' to see details.
    This message can be ignored if the mailbox in question is not part of your environment.
[...]

This only happens for shared mailboxes. Reason is that Microsoft Graph returns an error message when the 'aboutMe' attribute is queried for shared mailboxes. You can check this in Graph Explorer, for example:

The query 'https://graph.microsoft.com/v1.0/users/SharedMailbox@example.com?$select=userPrincipalName' is successful.

The query 'https://graph.microsoft.com/v1.0/users/SharedMailbox@example.com?$select=aboutMe' fails:

"code": "-1, Microsoft.SharePoint.Client.ResourceNotFoundException",
"message": "Exception of type 'Microsoft.SharePoint.Client.ResourceNotFoundException' was thrown.",

According to the documentation, shared mailboxes are to be queried as users via Graph, and 'aboutMe' is a valid user property.
This has worked for years, and suddenly started to fail around November 21, 2024, without being announced in a change.

A support case with Microsoft has been opened. This issue will be closed when Microsoft has solved the problem or when a new release of Set-OutlookSignatures with a fix gets released.

As this seems to be a bug in Microsoft Graph, embedding a fix in Set-OutlookSignatures is currently not the plan.

In the meantime, you can do the following to work around the problem:

Create a custom Graph config file, if you do not already use one:

Open the file '.\config\default graph config.ps1' and follow the instructions on how to create a custom Graph config file.

Open your custom Graph config file.
At the end of your custom Graph config file, add the following line of code which removes 'aboutMe' from the '$GraphUserProperties' array:
```
$GraphUserProperties = @($GraphUserProperties | Where-Object { $_ -ine 'aboutMe' })
```

If you need the 'aboutMe' attribute for signatures or out-of-office replies, there is currently no solution.

Originally created by @GruberMarkus on GitHub (Nov 21, 2024). Original GitHub issue: https://github.com/Set-OutlookSignatures/Set-OutlookSignatures/issues/130 ### Issue happens in the latest release - [X] I confirm that the issue happens in the latest release of Set-OutlookSignatures ### Previously solved issues and documentation - [X] I have searched through issues, discussions and documentation, but have not found an answer to my issue ### Code of Conduct - [X] I agree to follow this project's Code of Conduct ### What happened? Shared mailboxes are not found in Entra ID via Graph queries, although they exist. Set-OutlookSignatures shows the following output: ``` Get properties of each mailbox @2024-11-21T14:04:05+01:00@ [...] SharedMailbox@example.com Search for mailbox user object in Graph: No matching mailbox object found via Graph/Entra ID. Use parameter '-verbose' to see details. This message can be ignored if the mailbox in question is not part of your environment. [...] ``` This only happens for shared mailboxes. Reason is that Microsoft Graph returns an error message when the '`aboutMe`' attribute is queried for shared mailboxes. You can check this in Graph Explorer, for example: - The query '`https://graph.microsoft.com/v1.0/users/SharedMailbox@example.com?$select=userPrincipalName`' is successful. - The query '`https://graph.microsoft.com/v1.0/users/SharedMailbox@example.com?$select=aboutMe`' fails: ``` "code": "-1, Microsoft.SharePoint.Client.ResourceNotFoundException", "message": "Exception of type 'Microsoft.SharePoint.Client.ResourceNotFoundException' was thrown.", ``` According to the documentation, shared mailboxes are to be queried as users via Graph, and '`aboutMe`' is a valid user property.<br>This has worked for years, and suddenly started to fail around November 21, 2024, without being announced in a change. A support case with Microsoft has been opened. This issue will be closed when Microsoft has solved the problem or when a new release of Set-OutlookSignatures with a fix gets released. As this seems to be a bug in Microsoft Graph, embedding a fix in Set-OutlookSignatures is currently not the plan. In the meantime, you can do the following to work around the problem: 1. Create a custom Graph config file, if you do not already use one: - Open the file '`.\config\default graph config.ps1`' and follow the instructions on how to create a custom Graph config file. 2. Open your custom Graph config file. 3. At the end of your custom Graph config file, add the following line of code which removes '`aboutMe`' from the '`$GraphUserProperties`' array: ``` $GraphUserProperties = @($GraphUserProperties | Where-Object { $_ -ine 'aboutMe' }) ``` If you need the '`aboutMe`' attribute for signatures or out-of-office replies, there is currently no solution.

kerem closed this issue

2026-02-27 20:31:02 +03:00

kerem commented

2026-02-27 20:31:02 +03:00

Author

Owner

@GruberMarkus commented on GitHub (Nov 24, 2024):

Update 2024-11-24: Beside 'aboutMe', the following Delve properties of shared mailboxes can't be queried via Graph anymore: 'interests', 'pastProjects', 'schools', 'skills'.

The Microsoft support case is still open. It is not yet clear if this is a bug or a feature.

It could be that this is a bug that has to do with the retirement of Delve in December, for which Microsoft prepares changes in the backend. While the attributes mentioned before will not be deleted, but there will be other places where they can be edited - the problem described in this issue could be a side effect of this.

This issue will be updated as soon as there are relevant news from the Microsoft support case, the problem is solved, or a new release of Set-OutlookSignatures is published.

If you encounter the problem described in this issue, please follow the workaround in the issue description.

As 'aboutMe' is practically never used for signatures and out-of-office replies, and as the other attributes are not part of the default replacement variable set, it will very likely be removed in the next release of Set-OutlookSignatures. When Microsoft has solved the problems, you can add the attributes manually.

@GruberMarkus commented on GitHub (Nov 24, 2024): Update 2024-11-24: Beside '`aboutMe`', the following Delve properties of shared mailboxes can't be queried via Graph anymore: '`interests`', '`pastProjects`', '`schools`', '`skills`'. The Microsoft support case is still open. It is not yet clear if this is a bug or a feature. It could be that this is a bug that has to do with the retirement of Delve in December, for which Microsoft prepares changes in the backend. While the attributes mentioned before will not be deleted, but there will be other places where they can be edited - the problem described in this issue could be a side effect of this. This issue will be updated as soon as there are relevant news from the Microsoft support case, the problem is solved, or a new release of Set-OutlookSignatures is published. If you encounter the problem described in this issue, please follow the workaround in the issue description. As '`aboutMe`' is practically never used for signatures and out-of-office replies, and as the other attributes are not part of the default replacement variable set, it will very likely be removed in the next release of Set-OutlookSignatures. When Microsoft has solved the problems, you can add the attributes manually.

kerem commented

2026-02-27 20:31:03 +03:00

Author

Owner

@GruberMarkus commented on GitHub (Nov 28, 2024):

The Microsoft support case is now open for four days, and the support engineers could not even confirm that the Graph issue is reproducable until now, while I know of at least four tenants with the problem.

If the problem exists in your tenant, please leave a comment here.

@GruberMarkus commented on GitHub (Nov 28, 2024): The Microsoft support case is now open for four days, and the support engineers could not even confirm that the Graph issue is reproducable until now, while I know of at least four tenants with the problem. If the problem exists in your tenant, please leave a comment here.

kerem commented

2026-02-27 20:31:03 +03:00

Author

Owner

@GruberMarkus commented on GitHub (Dec 2, 2024):

Closing this issue as v4.16.0 has been publiched.

As 'aboutMe' is practically never used for signatures and out-of-office replies, and as the other attributes are not part of the default replacement variable set, they are removed in this release release of Set-OutlookSignatures.

@GruberMarkus commented on GitHub (Dec 2, 2024): Closing this issue as v4.16.0 has been publiched. As 'aboutMe' is practically never used for signatures and out-of-office replies, and as the other attributes are not part of the default replacement variable set, they are removed in this release release of Set-OutlookSignatures.

kerem referenced this issue

2026-02-27 20:31:16 +03:00

[PR #56] [CLOSED] Bump gittools/actions from 0.9.13 to 0.9.14 #101