Hi @Khaleel Shaik,
Azure recently introduced more granular permission checks for specific App Service features like Log Stream, Console, and Advanced Tools (Kudu). While earlier these features could be accessed with general "read-only" or inherited owner permissions, Log Stream now specifically requires write-level permissions on the App Service resource itself.
This means that even if you're an Owner at a subscription or resource group level, if Azure RBAC (Role-Based Access Control) hasn't granted explicit "Microsoft.Web/sites/write" permission, certain features like Log Stream will now be blocked. This behavior was likely introduced as part of security hardening updates to reduce the risk of unintended write access through diagnostic features.
To resolve this, you’ll need to ensure that the account you're using has explicit write permissions on the specific App Service resource.
- Go to your Azure Portal => Navigate to the App Service in question => Click Access control (IAM) from the left pane then Click "View my access" to confirm your exact role on the resource.
- If you don’t see
Microsoft.Web/sites/write
permission under Effective permissions, click + Add => Add role assignment. Assign a role like Contributor or Web Plan Contributor to your user account at the App Service level (not just at subscription/resource group level). Understand Azure RBAC
Built-in roles: Contributor
Reference:
https://learn.microsoft.com/en-us/azure/azure-monitor/fundamentals/roles-permissions-security
https://learn.microsoft.com/en-us/azure/app-service/troubleshoot-diagnostic-logs#stream-logs
If the answer is helpful, please click Accept Answer and kindly upvote it so that other people who faces similar issue may get benefitted from it.
Let me know if you have any further Queries.