Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Access to Service Bus message application properties for trigger and output

Open
#212 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
azure, java
Domain
backend, cloud

Research direction

Start with the @ServiceBusQueueTrigger and @ServiceBusQueueOutput entry points shown in the issue, then inspect how Azure Functions Java binding parameters and outputs represent messages. Determine whether application properties can be exposed for incoming and outgoing messages; done means a documented supported approach or a clearly scoped implementation path.

Written by the indexing model from the issue text.

Description

area:java-functions

When using the spring-cloud-azure-starter-servicebus library for regular Spring Boot applications you can use the wrapper class ServiceBusMessage to get and set the application properties (message.getApplicationProperties().put("key", "value"), for example).

But when I setup an Azure Function I have found no way to either get application properties from incoming message, nor being able to set it for outgoing messages.

@Component
public class UppercaseFunction {

    @FunctionName("uppercase")
    public void run(
             @ServiceBusQueueTrigger(/* config */) String message,
            @ServiceBusQueueOutput(/* config */) OutputBinding<String> output) {
        // How would I read application properties from the incoming message?
        output.setValue(message.toUpperCase());
        // How would I set application properties on the outgoing message?
    }
}

Have I missed some part of the documentation or is this not supported?

Dominant language
Java
Stars
45
Forks
49
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/azure-functions-java-library

All issues in Azure/azure-functions-java-library

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.