![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(131.20000000000002, 87%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERL%3C/text%3E%3C/svg%3E)
1,295 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(230.39999999999998, 60%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAJ%3C/text%3E%3C/svg%3E)
The issue you're experiencing is likely due to the Conditional Access insights and reporting feature still being configured to point to the Log Analytics Workspace in the old subscription. Since the workspace has been moved to a new subscription, the "Insights and reporting" feature in Entra ID (formerly Azure AD) needs to be updated to reference the new workspace location.
- Update the Diagnostic Settings for Entra ID
- Go to the Azure portal.
- Navigate to Entra ID (Azure AD).
- Under Monitoring, select Diagnostic settings.
- Find the existing diagnostic setting that sends logs to the Log Analytics Workspace.
- Update the setting to point to the new workspace in the current subscription.
- Reconfigure Conditional Access Insights and Reporting
- Go to the Azure portal.
- Navigate to Entra ID (Azure AD) > Security > Conditional Access > Insights and reporting.
- If the "Insights and reporting" blade is still pointing to the old workspace, you'll need to reconfigure it:
- Remove the current configuration by disconnecting it from the old Log Analytics Workspace.
- Reconnect or configure the "Insights and reporting" feature to use the Log Analytics Workspace in the new subscription.
- Ensure that you have the correct permissions in the new subscription to make these changes.
- Remove the current configuration by disconnecting it from the old Log Analytics Workspace.
- Verify and Assign Required Permissions
- Ensure that you have the necessary permissions in the new subscription to access and configure Log Analytics Workspaces. You might need roles such as Log Analytics Contributor or Monitoring Contributor.
- If needed, go to Access control (IAM) for the Log Analytics Workspace and ensure that you or your team have the correct roles assigned.
- Test the Configuration
- After making these updates, test the "Insights and reporting" feature under Conditional Access to ensure it is correctly retrieving logs from the new Log Analytics Workspace.
- Remove Old References (If Needed)
- If there are any lingering references to the old subscription that you no longer need, you may want to clean them up to avoid confusion.
By updating the Diagnostic Settings and ensuring that the Conditional Access insights feature is correctly configured to use the Log Analytics Workspace in the new subscription, you should be able to resolve the "Insufficient Permissions" error and regain full functionality.