---
title: "UCELI Cloud (@ucelicloud) | Hashnode"
description: "Cloud servers & domains | Practical guides to DNS, deployment and server operations. Read the latest articles by UCELI Cloud on Hashnode."
url: "https://hashnode.com/@ucelicloud"
---

@ucelicloud

# UCELI Cloud

@ucelicloud · Joined August 2026

Cloud servers & domains | Practical guides to DNS, deployment and server operations

[Website](https://uceli.com/)

## Comments

[Which Functions runtime and storage-extension/extension-bundle versions did you use for the role-removal test? There is a distinction to capture here: Microsoft's current permissions table lists Storage Blob Data Owner + Storage Queue Data Contributor for the blob trigger, and additional Storage Queue Data Contributor + Storage Account Contributor permissions in host-required storage. This is separate from the base AzureWebJobsStorage requirement: https://learn.microsoft.com/en-us/azure/azure-functions/manage-connections?pivots=functions-auth-identity#grant-permissions-to-an-identity Since your host and trigger share an account, including the exact versions and a fresh host start after removing the role would help readers reproduce your result. The specific denied operation in storage logs would also help explain any difference from the documented permissions.](https://hashnode.com/posts/my-azure-journey-2-blob-trigger-silence-a-missing-setting-and-making-managed-identity-work/6ac253980b766fff93c0b811/comment/6ac25f988f224414f9e66ab4)

Comment · Article · Oct 4 · 1 · [My Azure Journey #2: Blob Trigger Silence, a Missing Setting, and Making Managed Identity Work](https://hashnode.com/posts/my-azure-journey-2-blob-trigger-silence-a-missing-setting-and-making-managed-identity-work/6ac253980b766fff93c0b811)

[My first extra check would be the write cutover. For a site accepting comments, form submissions or orders, a successful restore rehearsal can still leave the destination behind the live database. One approach is a short, planned write freeze, a final database/uploads sync, validation, then the traffic switch. Keep the old origin from accepting writes while DNS caches expire, so you don't end up with two diverging databases. Once writes resume on the new host, rollback also needs a plan to preserve that new data. I'd lower DNS-only record TTL in advance; already-cached records retain their previous TTL (Cloudflare explains this here: https://developers.cloudflare.com/dns/faq/). Do you include a write-freeze/final-sync step for interactive sites?](https://hashnode.com/posts/moving-a-small-wordpress-site-restore-first-switch-dns-last/6ac11d969fe190618e05bfc5/comment/6ac25f045b2a5eb8f5c99b87)

Comment · Article · Oct 4 · [Moving a small WordPress site: restore first, switch DNS last](https://hashnode.com/posts/moving-a-small-wordpress-site-restore-first-switch-dns-last/6ac11d969fe190618e05bfc5)