Domain matching despite business verification rejection
Hello, I have been working with support in good faith after submitting a ticket request; they had asked me to submit proof of business name document and a domain registration document to verify that the domain I have on my profile matches the domain on the registration: " Dear Partner, Thank you for your inquiry about your Microsoft Partner Network account in Partner Center. We need more information from you to verify your Microsoft Partner Network account. To proceed with your request, and review your organization's status, please help us by emailing us the following documents. Please ensure that they are issued within the previous 12 months: Domain registration / Domain invoice at registration or renewal that lists Entity/Username and domain as it is stated on your account. Official business document, such as a business registration form, business charter, or articles of incorporation that lists Entity name and address as it is stated on your account. If not possible to provide additional documentation, please update your account information to match with documents already provided. List of supported file types and max. file size: screenshots (only from a source such as government) .pdf format Attachments larger than 8MB cannot be received by our system. Please advise if you are unable to provide smaller attachments. Thank you and best regards, Microsoft Operations " When I submitted initially, they said that there were unable to open the PDF documents that were attached (first time this has ever happened to me): "Dear Partner, We were unable to open any of the documents you have provided. Would you kindly send the documents again in the right format. Here is the list of the file types and max.file size that we require. screenshots (only from a source such as government) .pdf format Attachments larger than 8MB cannot be received by our system. Please advise if you are unable to provide smaller attachments. Thank you and best regards, Microsoft Operations" So I resubmitted the second time with screenshots showing that I have the PDF attached on my side and reattached the same PDFs as the last email. It appears that support then accepted the documents but sent this response: "Dear Partner, I am afraid that the provided document does not list the domain that appears on your Profile. If additional documentation containing this info is not available, please update your Profile to match the documents already provided. Thank you and best regards, Microsoft Operations" I am confident that the domain name on my profile exactly matched what is provided on the document, since it appears support accepted the domain registration document that I provided. Please see what should be attached as a screenshot below, showing the domain match: Domain registration document: Profile: Again, I have and am continuing to work with them to resolve this, so how can I get this moving forward? If further requested, I can provide the ticket number as well.Deploy Open Web UI on Azure VM via Docker: A Step-by-Step Guide with Custom Domain Setup.
Introductions Open Web UI (often referred to as "Ollama Web UI" in the context of LLM frameworks like Ollama) is an open-source, self-hostable interface designed to simplify interactions with large language models (LLMs) such as GPT-4, Llama 3, Mistral, and others. It provides a user-friendly, browser-based environment for deploying, managing, and experimenting with AI models, making advanced language model capabilities accessible to developers, researchers, and enthusiasts without requiring deep technical expertise. This article will delve into the step-by-step configurations on hosting OpenWeb UI on Azure. Requirements: Azure Portal Account - For students you can claim $USD100 Azure Cloud credits from this URL. Azure Virtual Machine - with a Linux of any distributions installed. Domain Name and Domain Host Caddy Open WebUI Image Step One: Deploy a Linux – Ubuntu VM from Azure Portal Search and Click on “Virtual Machine” on the Azure portal search bar and create a new VM by clicking on the “+ Create” button > “Azure Virtual Machine”. Fill out the form and select any Linux Distribution image – In this demo, we will deploy Open WebUI on Ubuntu Pro 24.04. Click “Review + Create” > “Create” to create the Virtual Machine. Tips: If you plan to locally download and host open source AI models via Open on your VM, you could save time by increasing the size of the OS disk / attach a large disk to the VM. You may also need a higher performance VM specification since large resources are needed to run the Large Language Model (LLM) locally. Once the VM has been successfully created, click on the “Go to resource” button. You will be redirected to the VM’s overview page. Jot down the public IP Address and access the VM using the ssh credentials you have setup just now. Step Two: Deploy the Open WebUI on the VM via Docker Once you are logged into the VM via SSH, run the Docker Command below: docker run -d --name open-webui --network=host --add-host=host.docker.internal:host-gateway -e PORT=8080 -v open-webui:/app/backend/data --restart always ghcr.io/open-webui/open-webui:dev This Docker command will download the Open WebUI Image into the VM and will listen for Open Web UI traffic on port 8080. Wait for a few minutes and the Web UI should be up and running. If you had setup an inbound Network Security Group on Azure to allow port 8080 on your VM from the public Internet, you can access them by typing into the browser: [PUBLIC_IP_ADDRESS]:8080 Step Three: Setup custom domain using Caddy Now, we can setup a reverse proxy to map a custom domain to [PUBLIC_IP_ADDRESS]:8080 using Caddy. The reason why Caddy is useful here is because they provide automated HTTPS solutions – you don’t have to worry about expiring SSL certificate anymore, and it’s free! You must download all Caddy’s dependencies and set up the requirements to install it using this command: sudo apt install -y debian-keyring debian-archive-keyring apt-transport-https curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/gpg.key' | sudo gpg --dearmor -o /usr/share/keyrings/caddy-stable-archive-keyring.gpg curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/debian.deb.txt' | sudo tee /etc/apt/sources.list.d/caddy-stable.list sudo apt update && sudo apt install caddy Once Caddy is installed, edit Caddy’s configuration file at: /etc/caddy/Caddyfile , delete everything else in the file and add the following lines: yourdomainname.com { reverse_proxy localhost:8080 } Restart Caddy using this command: sudo systemctl restart caddy Next, create an A record on your DNS Host and point them to the public IP of the server. Step Four: Update the Network Security Group (NSG) To allow public access into the VM via HTTPS, you need to ensure the NSG/Firewall of the VM allow for port 80 and 443. Let’s add these rules into Azure by heading to the VM resources page you created for Open WebUI. Under the “Networking” Section > “Network Settings” > “+ Create port rule” > “Inbound port rule” On the “Destination port ranges” field, type in 443 and Click “Add”. Repeat these steps with port 80. Additionally, to enhance security, you should avoid external users from directly interacting with Open Web UI’s port - port 8080. You should add an inbound deny rule to that port. With that, you should be able to access the Open Web UI from the domain name you setup earlier. Conclusion And just like that, you’ve turned a blank Azure VM into a sleek, secure home for your Open Web UI, no magic required! By combining Docker’s simplicity with Caddy’s “set it and forget it” HTTPS magic, you’ve not only made your app accessible via a custom domain but also locked down security by closing off risky ports and keeping traffic encrypted. Azure’s cloud muscle handles the heavy lifting, while you get to enjoy the perks of a pro setup without the headache. If you are interested in using AI models deployed on Azure AI Foundry on OpenWeb UI via API, kindly read my other article: Step-by-step: Integrate Ollama Web UI to use Azure Open AI API with LiteLLM Proxy
