-
Notifications
You must be signed in to change notification settings - Fork 442
Sharing Your Function App name privately
Bala G edited this page Oct 30, 2020
·
9 revisions
In many cases, for the Azure Functions team to properly investigate an issue with a Function App, we need to know your Function App name. If you are fine sharing your site name publicly (e.g. myfunctions.azurewebsites.net
), then you can just do that.
However, if you prefer not to share it publicly on the forum or in a Github issue (which we fully understand), there is an alternate way that will allow the team to know your app name without revealing it to others:
- In the portal manually run one of your functions
- In the log stream output the invocation will log a message like
2017-03-07T20:44:04.401 Function started (Id=561d7a18-2664-4807-b142-ee3738472667)
(See image below) - Share this UTC execution time and execution Id value and the Region your Function App is in. Those 3 pieces of information are enough for us to look up your details, and they do not reveal anything of interest to anyone but the Azure Functions team (so there is no concern about posting them publicly).
If for some reason the above steps do not work (may be because the app is broken completely / portal inaccessible etc) you can do the following
- Generate a new guid Ex: e620ba98-aca6-435f-adec-d9055ab9451c
- Send a request to [Function app name].azurewebsites.net/api/[GUID] Ex: myfunctions.azurewebsites.net/api/e620ba98-aca6-435f-adec-d9055ab9451c
- Share the UTC execution time and GUID used and the Region your Function App is in.
- Configuration Settings
- function.json
- host.json
- host.json (v2)
- Http Functions
- Function Runtime Versioning
- Official Functions developers guide
- Host Health Monitor
- Managing Connections
- Renaming a Function
- Retrieving information about the currently running function
- Site Extension Resolution
- Linux Consumption Regions
- Using LinuxFxVersion for Linux Function apps
- Out-of-proc Cancellation Tokens
- Assembly Resolution in Azure Functions
- ILogger
- Precompiled functions
- Official Functions C# developer reference
- Contributor Onboarding
- Development Process
- Deploying the Functions runtime as a private site extension
- Authoring & Testing Language Extensions
- Bindings in out-of-proc
- Language Extensibility
- Worker Capabilities
- Investigating and reporting issues with timer triggered functions not firing
- Sharing Your Function App name privately
- Azure Functions CLI release notes [moved here]
- Function App Zipped Deployment [deprecated]