Loki helm-chart won't persist to Azure Blob Containers

Hello community!

What are you trying to achieve?
I am trying to install a simple scalable Loki instance to my AKS environment. The full picture is to have Alloy collecting logs to send to Loki which is plugged into Grafana.
How are you trying to achieve it?
Following your documentation: Install the simple scalable Helm chart | Grafana Loki documentation
My configuration requires persisting to the Azure Blob Containers however I have so far been unable to succeed.
What Grafana version and what operating system are you using?
The helm chart builds Loki v3.2.0
What happened?
Loki deploys and seemingly runs fine- all the pods and running and look healthy- however nothing is being written to my blob containers and there is no error or log message telling me why not. The containers are precreated with access to read/write, however they remain empty.

My Plea
I am struggling to find a configuration to get this working between old versions of Loki, and the now decommed Loki-Stack and Loki-Distributed charts.
I appreciate anyone’s help that can be offered.

Values.yaml

loki:
  auth_enabled: false
  schemaConfig:
    configs:
      - from: "2024-04-01"
        store: tsdb
        object_store: azure
        schema: v13
        index:
          prefix: loki_index_
          period: 24h
  ingester:
    chunk_encoding: snappy
  tracing:
    enabled: true
  querier:
    max_concurrent: 4

  storage:
    type: azure
    azure:
      # Name of the Azure Blob Storage account
      accountName: redacted
      # Key associated with the Azure Blob Storage account
      accountKey: redacted
      # Comprehensive connection string for Azure Blob Storage account (Can be used to replace endpoint, accountName, and accountKey)
      connectionString: redacted
      # Flag indicating whether to use Azure Managed Identity for authentication
      useManagedIdentity: false
      # Flag indicating whether to use a federated token for authentication
      useFederatedToken: false
      # Timeout duration for requests made to the Azure Blob Storage account (in seconds)
      requestTimeout: 60
      # Domain suffix of the Azure Blob Storage service endpoint (e.g., core.windows.net)
      endpointSuffix: core.windows.net
    bucketNames:
      chunks: "loki-chunks"
      ruler: "loki-ruler"
      admin: "loki-admin"

deploymentMode: SimpleScalable
memberlist:
    service:
      publishNotReadyAddresses: true
backend:
  replicas: 3
read:
  replicas: 3
write:
  replicas: 3

# Disable minio storage
minio:
  enabled: false

# Zero out replica counts of other deployment modes
singleBinary:
  replicas: 0

ingester:
  replicas: 0
querier:
  replicas: 0
queryFrontend:
  replicas: 0
queryScheduler:
  replicas: 0
distributor:
  replicas: 0
compactor:
  replicas: 0
indexGateway:
  replicas: 0
bloomCompactor:
  replicas: 0
bloomGateway:
  replicas: 0

I am facing the similar issue. Did you get any way to solve this?
The ingester service is responsible for persisting data and shipping it to long-term storage. Give a shot if this might solve your issue
Also I wanted to pass down the Azure credentials as secrets, so that it won’t be exposed.