mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 16:26:09 +03:00
[GH-ISSUE #2144] Named locations "last modified" property always "invalid date" #1103
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#1103
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 @Lenwe666 on GitHub (Feb 21, 2024).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2144
Description
On the page Tenant administration > Conditional Access > Named locations
The property "last modified" for all items is always "invalid date", both for items made via CIPP and in Azure itself
Environment data
@github-actions[bot] commented on GitHub (Feb 21, 2024):
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!".
@Lenwe666 commented on GitHub (Feb 21, 2024):
I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.
@KelvinTegelaar commented on GitHub (Feb 21, 2024):
Again, support issue. This has to do with incorrect GDAP setups. Please stop creating issues or we'll be forced to ban you.
@Lenwe666 commented on GitHub (Feb 21, 2024):
How is that not a bug? The GDAP relations has all permissions it needs, like stated in your documentation, and confirmed when checking this from inside the application