This repository has been disabled. Access to this repository has been disabled by GitHub Staff due to a violation of GitHub's terms of service.

[jeep]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Actions Checkout

Discussion Details

I am getting this issue when I try to deploy:

This repository has been disabled.
Access to this repository has been disabled by GitHub Staff due to a violation of GitHub's terms of service. If you are the owner of the repository, you may reach out to GitHub Support for more information.

It started just today and I do not understand what I could possibly be doing that violated the TOS. How do I contact support to get more information?

[RossAFlood]

We are also getting CICD errors on startup if a yaml file contains the functions deploy action step
uses: Azure/functions-action@v1
Repo was locked up by github
https://github.com/Azure/functions-action

[rushilShetty]

Yup same here, all our Github action pipelines using this has stopped working! Great it's broken exactly on a Friday.

[rafaelherbert]

Same thing here. Going on since 14:59 UTC.

[jsoref]

• it's also mentioned in: https://learn.microsoft.com/en-my/answers/questions/5912595/github-action-azure-functions-action-down

[NicolasVitorP]

Hi @jeep! Rest assured, your personal repository did not violate GitHub's Terms of Service.

The error message you are seeing is misleading because of how GitHub Actions workflows evaluate dependencies. The issue is that the official Microsoft/Azure repository for the deployment step you are using (uses: Azure/functions-action@v1) was accidentally flagged and disabled by GitHub's automated safety systems today.

Because your pipeline tries to pull code from that specific Azure repository during runtime, your entire workflow crashes with that scary Terms of Service error block.

What you can do right now:

1. Do not panic or spam GitHub Support: Since this affects a massive number of global enterprise deployments, Azure and GitHub engineering teams are already actively communicating internally to get the official Azure/functions-action repository whitelisted and restored.
2. Monitor the situation: Keep an eye on the official Microsoft thread linked by @jsoref or look out for updates on the GitHub Status Page.
3. Temporary Workaround (If critical): If your Friday deployment cannot wait for the repository to be unbanned, you would need to temporarily rewrite your CI/CD step to deploy via the standard Azure CLI core commands (az functionapp deploy) instead of relying on the pre-packaged GitHub Action marketplace wrapper.

Hang tight! This should be resolved as soon as a GitHub staff member manually overrides the automated ban on Azure's repository.

[rushilShetty]

@NicolasVitorP Github status pages shows all green and "All systems operational", yet when I go to the repo it's still disabled! Is Github actually aware of this? Is there an actual bug ticket for this? To me it seems like they are not aware of this at all.

[NicolasVitorP]

@rushilShetty I totally get your frustration, especially with the GitHub Status page showing "All Systems Operational." It feels like shouting into a void.

The reason the status page is all green is that GitHub Status only monitors infrastructure availability (e.g., whether the API servers, database nodes, or Action runners are physically up and accepting jobs). It does not track automated safety/ToS flags or individual repository bans, even if that repository happens to be an official Microsoft package used by thousands. To the status page robots, the system itself is "working perfectly"—it's just serving a block page.

Is GitHub actually aware?

Yes, absolutely. Behind the scenes, the Microsoft Azure engineering teams and GitHub security operations are definitely awake and handling this. Because Azure Functions is a core enterprise offering, this block creates immediate escalation alerts internally.

The delay happens because overturning a Terms of Service block (even a false positive) requires manual legal/security override compliance steps within GitHub to prevent actual malicious code from slipping through.

What to do while we wait:

If your pipelines are completely dead and you cannot afford to wait for the weekend security sync to unban the repo, you should implement the Azure CLI fallback inside your .github/workflows/ YAML file right now to unblock your team:

- name: 'Log in via Azure CLI'
  uses: azure/login@v2
  with:
    creds: ${{ secrets.AZURE_CREDENTIALS }}

- name: 'Deploy Function App via CLI'
  run: |
    az functionapp deploy --resource-group <your-rg> --name <your-app-name> --src-path <your-zip-or-artifact>

[jsoref]

Access appears to have been restored.

• this ticket asks for an explanation: Request for Post-Incident Transparency Regarding Azure/functions-action Outage Azure/functions-action#363