mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 16:26:09 +03:00
[GH-ISSUE #1784] "Set Technical Contact e-mail" Standard and others... #943
Labels
No labels
API
Feature
NotABug
NotABug
Planned
Sponsor Priority
Sponsor Priority
bug
documentation
duplicate
enhancement
needs more info
no-activity
no-priority
not-assigned
pull-request
react-conversion
react-conversion
roadmap
security
stale
unconfirmed-by-user
unconfirmed-by-user
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/CIPP#943
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @akraker99 on GitHub (Oct 5, 2023).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1784
Description
I have tried setting the Technical Contact e-mail in the individual standards section but it does not appear to be taking effect. I have tried at the All Tenants level and at individual tenant levels. I have also tried pushing the standards and waiting several hours for the normal 3 hour interval push.
All Permission checks come back good. I can verify that the address has not changed both by looking at the Org Contact settings in the GUI and by using Get-MsolCompanyInformation | FL DisplayName, TechnicalNotificationEmails
Unless this is setting a different address?
Along these lines, I am unsure about what the other setttings in CIPP are supposed to set (Security, Marketing and General). The only other contact available to change with Set-MsolCompanyInformation according to Microsoft is the Marketing Contact
https://learn.microsoft.com/en-us/powershell/module/msonline/set-msolcompanycontactinformation?view=azureadps-1.0
Environment data
@github-actions[bot] commented on GitHub (Oct 5, 2023):
Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://docs.cipp.app/
If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.".
Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".
@KelvinTegelaar commented on GitHub (Oct 5, 2023):
Not a bug, support question. as a sponsor you can get support.