heroku-buildpack-git-lfs | Heroku buildpack for git-lfs | Platform As A Service library

Your Jelastic provider doesn't allow Telegraf to be installed on this type of node. You can ask them to allow that. Thanks

Thank you rickvdbosch. Posting your suggestion as an answer to help other community members.

• You can set Health alerts. "Azure Service Health notifies you about Azure service incidents and planned maintenance so you can take action to mitigate downtime. Configure customizable cloud alerts and use your personalized dashboard to analyze health issues, monitor the impact to your cloud resources, get guidance and support, and share details and updates."

can we add specific service in the service health?

• In Service Health, choose the Potential impact tab to see the specific list of resources you own that might be impacted by the issue. You can download a CSV list of these resources to share with your team.

No. If you want an entirely containerized solution, you'll need to find or build containerized alternatives to these Azure services.

You can use private link to do this. In terms of performance it depends on your IaaS Architecture and in what KPI you define. Here is a link to a good Microsoft document: zero-trust-part-1-networking

Like I said in the comments, it's been fixed for some reason after a while but I didn't do anything different than before except that I've changed maintenance mode through the website - not via CLI. I performed the following changes.

• Turn on maintenance mode through website
• Entered this in the CLI: heroku ps:scale web=0 -a myapp
• Resources are all offline

I provided these settings in case people got similar issues.

I got the answer, so I thought it will help the community if someone has the same question.

The PaaS - PaaS traffic stays entirely within Azure backbone network. Link here

I'm not sure if this will fix all your issues, but there is a syntax error there. In your connection string you put authentication="Azure Active Directory"" that is a syntax error because your double quote actually ends the string... get rid of the "" around the azure active directory. like. authentication=Azure Active Directory"; that would at least get rid of the syntax error.

I can reproduce your issue, first, make sure the group is in the same tenant of your service connection.

Then navigate to the Azure portal -> Azure Active Directory -> App registrations -> find the AD App Registration related to your service connection, follow the steps below to add the Application permission Directory.Read.All of Azure Active Directory Graph(not Microsoft Graph), don't forget to click the Grant admin consent for xxx button at last.

After adding the permission, there is some delay(30m - 1h), then test the command, it works.

To run the command Set-AzKeyVaultAccessPolicy, it will call the Azure AD Graph to validate the $objectid you passed. In could shell, it uses the credential of your user account, it works means your user account has the permission. In devops, the service principal has no permission to do that by default.

To solve the issue, the easiest way is to use the -BypassObjectIdValidation parameter like below, then it will work fine.