[GH-ISSUE #2999] 403 Request Failed with status code 403 #1493

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

Originally created by @aleffler-NU on GitHub (Dec 4, 2024).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2999

Description

I imported my Conditional access policies and named locations from one of my environments and after I did that. It started giving me an 403 error and it's unable to list any CA templates now.

  1. Go to Tenant administration
  2. Go to Conditional Access
  3. Go to CA Templates

403Error

Environment data

Sponsored
Front End Version Number: 6.4.1
Back End Version Number: 6.5.4
Tenant Cache Clear: True
Token Cache Clear: False
Originally created by @aleffler-NU on GitHub (Dec 4, 2024). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2999 ### Description I imported my Conditional access policies and named locations from one of my environments and after I did that. It started giving me an 403 error and it's unable to list any CA templates now. 1. Go to Tenant administration 2. Go to Conditional Access 3. Go to CA Templates ![403Error](https://github.com/user-attachments/assets/90931c03-a5cf-45d8-aac9-1c27b719a9e2) ### Environment data ```PowerShell Sponsored Front End Version Number: 6.4.1 Back End Version Number: 6.5.4 Tenant Cache Clear: True Token Cache Clear: False ```
kerem 2026-03-02 13:44:40 +03:00
Author
Owner

@github-actions[bot] commented on GitHub (Dec 4, 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!".

<!-- gh-comment-id:2518492559 --> @github-actions[bot] commented on GitHub (Dec 4, 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!".
Author
Owner

@aleffler-NU commented on GitHub (Dec 4, 2024):

I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.

<!-- gh-comment-id:2518514356 --> @aleffler-NU commented on GitHub (Dec 4, 2024): I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.
Author
Owner

@aleffler-NU commented on GitHub (Dec 12, 2024):

Hello, I'm unsure if this was closed as an improperly submitted Bug request but we are still dealing with the same issue. Error message on Conditional Access Templates? Any idea on how we can fix this?

Adrian Leffler
Owner, Nodes Up I.T. Solutions
t: 520-585-4750
e: @.*** | w: www.nodesup.com
a: 3131 N. Country Club Road #110, Tucson, 85716
From: KelvinTegelaar @.>
Sent: Thursday, December 12, 2024 8:49 AM
To: KelvinTegelaar/CIPP @.
>
Cc: Adrian Leffler @.>; Author @.>
Subject: Re: [KelvinTegelaar/CIPP] 403 Request Failed with status code 403 (Issue #2999)

You don't often get email from @.@.>. Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification

Closed #2999https://github.com/KelvinTegelaar/CIPP/issues/2999 as completed.

Reply to this email directly, view it on GitHubhttps://github.com/KelvinTegelaar/CIPP/issues/2999#event-15636969317, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BMRZSNKLJNPSHBRW3H25YZT2FGV5NAVCNFSM6AAAAABTA7O4TOVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJVGYZTMOJWHEZTCNY.
You are receiving this because you authored the thread.Message ID: @.@.>>

<!-- gh-comment-id:2539500957 --> @aleffler-NU commented on GitHub (Dec 12, 2024): Hello, I'm unsure if this was closed as an improperly submitted Bug request but we are still dealing with the same issue. Error message on Conditional Access Templates? Any idea on how we can fix this? Adrian Leffler Owner, Nodes Up I.T. Solutions t: 520-585-4750 e: ***@***.*** | w: www.nodesup.com a: 3131 N. Country Club Road #110, Tucson, 85716 From: KelvinTegelaar ***@***.***> Sent: Thursday, December 12, 2024 8:49 AM To: KelvinTegelaar/CIPP ***@***.***> Cc: Adrian Leffler ***@***.***>; Author ***@***.***> Subject: Re: [KelvinTegelaar/CIPP] 403 Request Failed with status code 403 (Issue #2999) You don't often get email from ***@***.******@***.***>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> Closed #2999<https://github.com/KelvinTegelaar/CIPP/issues/2999> as completed. - Reply to this email directly, view it on GitHub<https://github.com/KelvinTegelaar/CIPP/issues/2999#event-15636969317>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BMRZSNKLJNPSHBRW3H25YZT2FGV5NAVCNFSM6AAAAABTA7O4TOVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJVGYZTMOJWHEZTCNY>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
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#1493
No description provided.