[GH-ISSUE #1297] Exchange Online tenancy standards are duplicated into SharePoint Online standards #721

Closed
opened 2026-03-02 12:44:38 +03:00 by kerem · 3 comments
Owner

Originally created by @ITbuilderTechOps on GitHub (Jan 9, 2023).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1297

Description

Exchange Online tenancy standards are duplicated into SharePoint Online standards after upgrading to frontend version 2.19.1

Tenant Administration > Standards > Edit Individual Standards
image

Environment data

Frontend - 2.19.1
Backend - 2.8.0
Azure hosted
Originally created by @ITbuilderTechOps on GitHub (Jan 9, 2023). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1297 ### Description Exchange Online tenancy standards are duplicated into SharePoint Online standards after upgrading to frontend version 2.19.1 Tenant Administration > Standards > Edit Individual Standards ![image](https://user-images.githubusercontent.com/113116532/211327750-8042971c-830c-4cca-8cd5-157cc8aa4b1c.png) ### Environment data ```PowerShell Frontend - 2.19.1 Backend - 2.8.0 Azure hosted ```
kerem 2026-03-02 12:44:38 +03:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 9, 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://kelvintegelaar.github.io/CIPP
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!".

<!-- gh-comment-id:1375685150 --> @github-actions[bot] commented on GitHub (Jan 9, 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://kelvintegelaar.github.io/CIPP 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!".
Author
Owner

@KelvinTegelaar commented on GitHub (Jan 9, 2023):

Already resolved

<!-- gh-comment-id:1375704928 --> @KelvinTegelaar commented on GitHub (Jan 9, 2023): Already resolved
Author
Owner

@ITbuilderTechOps commented on GitHub (Jan 9, 2023):

Thanks Kelvin, is there an ETA when the resolved release will be pushed to the repo?

I updated our CIPP app to 2.19.1 today and the bug was present, and from what I can see the last commit was 3 weeks ago.

<!-- gh-comment-id:1375807971 --> @ITbuilderTechOps commented on GitHub (Jan 9, 2023): Thanks Kelvin, is there an ETA when the resolved release will be pushed to the repo? I updated our CIPP app to 2.19.1 today and the bug was present, and from what I can see the last commit was 3 weeks ago.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/CIPP#721
No description provided.