Missing Application Setting Alert in function app diagnose and solve problems link. the configuration is for a event hub namespace connection though app works fine.

Question

Missing Application Setting Alert in function app diagnose and solve problems link. the configuration is for a event hub namespace connection though app works fine.

Abhishake Jaiswal 160

we are seeing an critical Alert as
Missing Application Settings detected
with message as :

The following Application Settings are referenced in Function bindings but not configured in the Function App. This can cause execution errors

Function: <<funcappName>>/<<funcName>>, Binding parameter: eventHubMessage, Application setting: pn_EventHubConnection

The binding file entry is like

{
      "name": "eventHubMessage",
      "direction": "out",
      "type": "eventHub",
      "eventHubName": "%name_EventHub%",
      "connection": "name_EventHubConnection"
    }

and the application setting looks like

{
    "name": "name_EventHubConnection__fullyQualifiedNamespace",
    "value": "eventhubName.servicebus.windows.net",
    "slotSetting": false
  }

Is this way of adding the property not advisable by MS ?
our app seems to be working fine though with Alert.

Sai Prabhu Naveen Parimi 3,970 Reputation points Microsoft External Staff Moderator

2025-08-05T08:26:45.5666667+00:00

@Abhishake Jaiswal

Can you confirm the exact name of the application setting that your function is trying to access?

Have you tried removing any unwanted suffixes from the application setting names?

Are there any other binding parameters in your function that are also showing missing settings?

What version of Azure Functions are you using? Are you using a particular framework or language?

Have you checked the logs to see if there are any specific execution errors related to this alert?
Abhishake Jaiswal 160 Reputation points

2025-08-06T09:14:49.18+00:00

hi Sai Thanks for replying.

Below are your answers
Q: Can you confirm the exact name of the application setting that your function is trying to access?
A: name_EventHubConnection (as mentioned in binding mentioned initially)

Q: Have you tried removing any unwanted suffixes from the application setting names?
A. We added the suffix "__fullyQualifiedNamespace" to application property because without it we were not able to connect function app to event hub in first place. So we did that last year and since then we are using this suffix. Saw the critical warning message first time in function app. are you aware if there has been some change ?

Q: Are there any other binding parameters in your function that are also showing missing settings?
A : No the error message is only for this specific property

Q: What version of Azure Functions are you using? Are you using a particular framework or language?
A: function runtime version ~4. We are using node js function app.

Q: Have you checked the logs to see if there are any specific execution errors related to this alert?
A; Yes i have checked the logs there is no error related to this application property.

we do randomly get below error in function app.
Message

An exception occurred while receiving events for Event Hub: <<appname>>-evh-prd (Consumer Group: target-ecg, Partition Id: 0); Operation Id: d4d57e3e-XXXXXXXXXXXXX0. Error Message: New receiver P0-XXXXXXXXXXd with higher epoch of 0 is created hence current receiver P0-XXXXXXXXXXX-8245e62a19b5 with epoch 0 is getting disconnected. If you are recreating the receiver, make sure a higher epoch is used. TrackingId:7e46db95000137a000305eef68922648_G25_B28, SystemTracker:<AppName>>-evhns-prd:eventhub:<<AppName>>-evh-prd~1023|target-ecg, Timestamp:2025-08-05T16:03:10 (<<AppName>>-evh-prd). For troubleshooting information, see https://aka.ms/azsdk/net/eventhubs/exceptions/troubleshoot

but as per below link, this seems to be just informational message
https://learn.microsoft.com/en-us/answers/questions/2261749/new-receiver-with-higher-epoch-of-0-is-created-hen
Sai Prabhu Naveen Parimi 3,970 Reputation points Microsoft External Staff Moderator

2025-08-07T09:33:29.45+00:00
Hello @Abhishake Jaiswal

Thanks for sharing the details.

The message you’re seeing:

"New receiver with higher epoch of '0' is created hence current receiver with epoch '0' is getting disconnected"

is expected when using the Event Hubs SDK with load balancing, particularly with EventProcessorClient. This usually happens during normal partition rebalancing.

About every 30 seconds, the SDK checks partition ownership through the BlobCheckpointStore. One instance may take over a partition from another, causing the previous receiver to disconnect to ensure exclusive access, even if both have the same epoch (0).

Since you’ve verified that the app is running smoothly, events are processed as expected, and there are no errors in the logs, the system is functioning as designed. This message is just informational, and no action is required.

References:

Microsoft Docs – Covers this specific scenario: https://learn.microsoft.com/en-us/azure/developer/java/sdk/troubleshooting-messaging-event-hubs-processor#current-receiver-receiver_name-with-epoch-0-is-getting-disconnected

Microsoft Tech Community Blog – Provides an in-depth explanation of Epoch behavior: https://techcommunity.microsoft.com/blog/azurepaasblog/eventhub-the-behavior-of-eph-sdk-behavior-of-epoch/3888275

I hope this helps clear things up!
Sai Prabhu Naveen Parimi 3,970 Reputation points Microsoft External Staff Moderator

2025-08-08T07:15:07.9933333+00:00

@Abhishake Jaiswal

I wanted to follow up to see if you’ve had an opportunity to look over my earlier response. Please let me know if you have any further questions.
Abhishake Jaiswal 160 Reputation points

2025-08-09T10:57:10.85+00:00

hi Sai

Thanks for your response.
my problem is not EventHub error message. I agree with the links and explanation you gave for those
The issue here is the critical Alert getting shown in Azure function app in production. On clicking Diagnose and Solve problem, this critical Alert says the property for event hub connection is not configured in app.

click on view more details

just trying to ensure that we do not have sudden impact to production.

will you be able to confirm if this Alert is by mistake\informational or do we need to take any action?
Let me know if you want more details.

Regards

Abhishake
Sai Prabhu Naveen Parimi 3,970 Reputation points Microsoft External Staff Moderator

2025-08-11T05:16:02.3166667+00:00
@Abhishake Jaiswal

Please add the following application setting in the Function App configuration and then restart the app:

name_EventHubConnection = ""

After the restart, could you check if you still see the alert
Abhishake Jaiswal 160 Reputation points

2025-08-11T05:20:30.7766667+00:00
hi Sai,

The property is already there.

can you please go through my initial query again ?

The function app binding file entry is like

{ "name": "eventHubMessage", "direction": "out", "type": "eventHub", "eventHubName": "%name_EventHub%", "connection": "name_EventHubConnection" }

and the application setting looks like in Function app

{
Sai Prabhu Naveen Parimi 3,970 Reputation points Microsoft External Staff Moderator

2025-08-11T11:57:27.4366667+00:00

@Abhishake Jaiswal

Could you please check the private message.

Here is the reference link on how to access & data retention policy of private messages in Microsoft Q&A.
Praveen Kumar Gudipudi 2,295 Reputation points Microsoft External Staff Moderator

2025-09-17T06:55:27.85+00:00

Hello Abhishake Jaiswal,

Please go through the similar issue in Critical availability error.

Suggested resolution: I have modified the risk alert logic so it should not report an issue when using managed identity anymore. If possible, please verify that the issue is no longer present and report back.

Please follow above suggested steps and let us know with an update.
Abhishake Jaiswal 160 Reputation points

2025-09-22T07:14:42.04+00:00

hi @Praveen Kumar Gudipudi ,

in the link you have given there are no steps to modify risk alert logic.
we can still see that critical Alert in app.

Regards

Abhishake Jaiswal

Praveen Kumar Gudipudi 2,295 Microsoft External Staff Moderator

Hello Abhishake Jaiswal,

Could you please update your app setting as below:

App settings:

Name	Value
name_EventHubConnection	Endpoint=sb://mynamespace.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=xxx;EntityPath=myeventhub
name_EventHubConnection	Endpoint=sb://mynamespace.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=xxx;EntityPath=myeventhub

Get your Event Hub connection string

In the Azure portal:

Go to your Event Hub Namespace.

Under Settings, select Shared access policies.

Click on a policy with Send and/or Listen permissions (usually RootManageSharedAccessKey).

Copy the Connection string – primary key. It looks like this: """Endpoint=sb://<your-eventhub-namespace>.servicebus.windows.net/;SharedAccessKeyName=<key-name>;SharedAccessKey=<key>;EntityPath=<eventhub-name>"""

Please configure above setting and let me know if you're still getting this allert.

Praveen Kumar Gudipudi 2,295 Reputation points Microsoft External Staff Moderator

2025-09-29T12:31:54.2666667+00:00

Hello Abhishake Jaiswal,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Your answer

Sai Prabhu Naveen Parimi 3,970 Reputation points Microsoft External Staff Moderator

2025-08-05T08:26:45.5666667+00:00

@Abhishake Jaiswal

Can you confirm the exact name of the application setting that your function is trying to access?

Have you tried removing any unwanted suffixes from the application setting names?

Are there any other binding parameters in your function that are also showing missing settings?

What version of Azure Functions are you using? Are you using a particular framework or language?

Have you checked the logs to see if there are any specific execution errors related to this alert?
Sai Prabhu Naveen Parimi 3,970 Reputation points Microsoft External Staff Moderator

2025-08-07T09:33:29.45+00:00

Hello @Abhishake Jaiswal

Thanks for sharing the details.

The message you’re seeing:

"New receiver with higher epoch of '0' is created hence current receiver with epoch '0' is getting disconnected"

is expected when using the Event Hubs SDK with load balancing, particularly with EventProcessorClient. This usually happens during normal partition rebalancing.

About every 30 seconds, the SDK checks partition ownership through the BlobCheckpointStore. One instance may take over a partition from another, causing the previous receiver to disconnect to ensure exclusive access, even if both have the same epoch (0).

Since you’ve verified that the app is running smoothly, events are processed as expected, and there are no errors in the logs, the system is functioning as designed. This message is just informational, and no action is required.

References:

Microsoft Docs – Covers this specific scenario: https://learn.microsoft.com/en-us/azure/developer/java/sdk/troubleshooting-messaging-event-hubs-processor#current-receiver-receiver_name-with-epoch-0-is-getting-disconnected

Microsoft Tech Community Blog – Provides an in-depth explanation of Epoch behavior: https://techcommunity.microsoft.com/blog/azurepaasblog/eventhub-the-behavior-of-eph-sdk-behavior-of-epoch/3888275

I hope this helps clear things up!
Sai Prabhu Naveen Parimi 3,970 Reputation points Microsoft External Staff Moderator

2025-08-08T07:15:07.9933333+00:00

@Abhishake Jaiswal

I wanted to follow up to see if you’ve had an opportunity to look over my earlier response. Please let me know if you have any further questions.
Abhishake Jaiswal 160 Reputation points

2025-08-09T10:57:10.85+00:00

hi Sai

Thanks for your response.
my problem is not EventHub error message. I agree with the links and explanation you gave for those
The issue here is the critical Alert getting shown in Azure function app in production. On clicking Diagnose and Solve problem, this critical Alert says the property for event hub connection is not configured in app.

click on view more details

just trying to ensure that we do not have sudden impact to production.

will you be able to confirm if this Alert is by mistake\informational or do we need to take any action?
Let me know if you want more details.

Regards

Abhishake
Sai Prabhu Naveen Parimi 3,970 Reputation points Microsoft External Staff Moderator

2025-08-11T05:16:02.3166667+00:00

@Abhishake Jaiswal

Please add the following application setting in the Function App configuration and then restart the app:

name_EventHubConnection = ""

After the restart, could you check if you still see the alert
Abhishake Jaiswal 160 Reputation points

2025-08-11T05:20:30.7766667+00:00

hi Sai,

The property is already there.

can you please go through my initial query again ?

The function app binding file entry is like

{ "name": "eventHubMessage", "direction": "out", "type": "eventHub", "eventHubName": "%name_EventHub%", "connection": "name_EventHubConnection" }

and the application setting looks like in Function app

{
Sai Prabhu Naveen Parimi 3,970 Reputation points Microsoft External Staff Moderator

2025-08-11T11:57:27.4366667+00:00

@Abhishake Jaiswal

Could you please check the private message.

Here is the reference link on how to access & data retention policy of private messages in Microsoft Q&A.
Praveen Kumar Gudipudi 2,295 Reputation points Microsoft External Staff Moderator

2025-09-17T06:55:27.85+00:00

Hello Abhishake Jaiswal,

Please go through the similar issue in Critical availability error.

Suggested resolution: I have modified the risk alert logic so it should not report an issue when using managed identity anymore. If possible, please verify that the issue is no longer present and report back.

Please follow above suggested steps and let us know with an update.
Abhishake Jaiswal 160 Reputation points

2025-09-22T07:14:42.04+00:00

hi @Praveen Kumar Gudipudi ,

in the link you have given there are no steps to modify risk alert logic.
we can still see that critical Alert in app.

Regards

Abhishake Jaiswal
Praveen Kumar Gudipudi 2,295 Reputation points Microsoft External Staff Moderator

2025-09-25T12:19:48.3033333+00:00

Hello Abhishake Jaiswal,

Could you please update your app setting as below:

App settings:

Name Value

name_EventHubConnection Endpoint=sb://mynamespace.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=xxx;EntityPath=myeventhub

name_EventHubConnection Endpoint=sb://mynamespace.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=xxx;EntityPath=myeventhub

Get your Event Hub connection string

In the Azure portal:

Go to your Event Hub Namespace.

Under Settings, select Shared access policies.

Click on a policy with Send and/or Listen permissions (usually RootManageSharedAccessKey).

Copy the Connection string – primary key. It looks like this: """Endpoint=sb://<your-eventhub-namespace>.servicebus.windows.net/;SharedAccessKeyName=<key-name>;SharedAccessKey=<key>;EntityPath=<eventhub-name>"""

Please configure above setting and let me know if you're still getting this allert.
Praveen Kumar Gudipudi 2,295 Reputation points Microsoft External Staff Moderator

2025-09-29T12:31:54.2666667+00:00

Hello Abhishake Jaiswal,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.