Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 10 hours ago.
Improve this question
I registered a domain, let’s say example.com, and want Microsoft Azure to do the web hosting so I can send and receive emails as me#example.com. How do I do that?
I basically want to get rid of my current web hosting company (myhosting.example) and want to use Azure instead because it is more convenient.
As a client I want to use Microsoft Outlook on my PC at home.
Is that even possible?
As part of azure you can access office 365. It uses the same custom domains. You will require a license for office 365. These start at around $4.
Using office 365 you can both send and relay e-mails.
Access of 365 is via https://portal.office.com
You can host your custom domains in Azure using Azure DNS also you can build your own mail servers ..etc. (Build VMs then install ur mail server)
However I would recommend using Office 365, if its about hosting a mail server.
Related
Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 4 months ago.
Improve this question
I am trying to deploy a website via Azure Devops to an IIS server that has the "Default Web Site" started with a binding on port 80.
I want my website to run on port 80.
I am using the "IIS Web App Manage" task. When I run my deployment on this machine, I get an error:
[error]Binding (http / * : 80 : ) already exists for a different website ("site "default web site" (id:1,bindings:http/*:80:,state:stopped)"), change the port and retry the operation.
I have stopped the default web site but I still get the same error because the binding already exists.
I have tried using the IIS Web App Manage task to remove the binding on the Default web site but there does not appear to be a way to do this. I do not see another task that will perform this task.
I am trying to automate this for future deployment via Azure Devops so I do not have to change the bindings or remove the default website by hand.
I am trying to automate this for future deployment via Azure Devops so I do not have to change the bindings or remove the default website by hand.
Based on my experience, you could add Run PowerShell on Target Machines task before IIS Web App Manage task with following script
Get-WebBinding -Port 80 -Name "Default Web Site" | Remove-WebBinding
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I'd like to make a Microsoft Flow workflow in the cloud use an on-premises website.
I'm beginning to think it's not possible.
To begin testing, I setup a simple flow based on a recurrence.
Each recurrence, it tries to access a website on my local HTTP website on my domain using an HTTP step.
I've setup an on-premises data gateway on local machine and in the azure portal, but have no way of associating that with a flow or HTTP step.
Microsoft documentation says the data gateways don't support HTTPs traffic, so I made sure I had a working HTTP binding for the site.
I'm not sure if I could design a custom connector for HTTP or not. This is not a web api, this is just a standard unsecured website behind my firewall that has some company related data on it.
It seems to me like I shouldn't be the only one wanting to do this.
Any ideas?
Currently you cannot do that directly. How about exposing your on-premise HTTP Endpoint via Azure Relay or some other technology.
There is, however, an On-Premises Data Gateway for Microsoft Flow (which internally uses Azure Service Bus). This !! currently !! (2017-07-24) !! supports the following data sources:
SQL Server
SharePoint
Oracle
Informix
Filesystem
DB2
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 3 years ago.
Improve this question
This is more a theoretical question than a practical one.
I have four different App Services in Azure (each one for dev, tst, acc and prd), and I want to secure them with SSL.
So, in the portal Azure, I select one of the endpoints something-dev.azurewebsites.net and I go to SSL Certificates (I uploaded a certificate there already). Then when I click to add a SSL Binding, a Hostname is required.
I can create a hostname by using the Custom Domains option. But this will imply in some costs and extra work. It's not expansive, and the amount of work is not a lot, but what I'm wondering is:
If I can access already my App Service by using its endpoint (something-dev.azurewebsites.net), why can't I just add SSL binding to this endpoint directly? Why do I need a Custom Domain for it?
I might be lacking some knowledge about SSL, so I'd really appreciate an explanation. Thanks.
You can use the .azurewebsites.net endpoint with SSL directly already (out of the box). The reason not to do this for production, however, is that that particular domain is not owned by you, it's shared amongst every other web app running on Azure. So it's usually fine for dev/test environments and proving that your site works on https: ok, but when going to production you should really use your own custom domain - the settings you're referring to are leading you down that path, so you can then import the corresponding certificate.
From the relevant app services Azure documentation
To secure with HTTPS an app that has a custom domain name, you add a certificate for that domain name. By default, Azure secures the *.azurewebsites.net wildcard domain with a single SSL certificate, so your clients can already access your app at https://.azurewebsites.net. But if you want to use a custom domain, like contoso.com, www.contoso.com, and *.contoso.com, the default certificate can't secure that. Furthermore, like all wildcard certificates, the default certificate is not as secure as using a custom domain and a certificate for that custom domain.
Because you don't own that domain name! instead, its owned by "azurewebsites.net". The domain your using is simply a sub-domain which you have NO control over. So, if you want an SSL certificate you must lease a domain from a registrar.
Actually, you don't need a custom domain to use your own certificate. As I commented above, I had forgotten how to do it. But I've remembered now.
In your web app service settings menu go to Application Settings.
Scroll down to app settings.
In the Key box type "WEBSITE_LOAD_CERTIFICATES"
In the Value box type the thumbprint of your custom SSL certificate.
Edit: Don't forget to actually upload the SSL cert.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
Will Azure Websites support virtual network in the future. To enable an Azure Website to connect to VM:s and Cloud Services using a local ip within Azure instead of needing to open up the servers and services to everyone by using the public IP.
Is that something that's actively being developed or is such a feature way into the future. Or both.
i think feature has been there for a while, please checkout below article
https://azure.microsoft.com/en-us/blog/azure-websites-virtual-network-integration/
Quote:
Azure Websites is happy to announce support for integration between
your Azure VNET and your Azure Websites. While you cannot place your
Azure Website in an Azure VNET, the Virtual Network feature grants
your website access to resources running your VNET. This includes
being able to access web services or databases running on your Azure
Virtual Machines. If your VNET is connected to your on premise network
with Site to Site VPN, then your Azure Website will now be able to
access on premise systems through the Azure Websites Virtual Network
feature. This feature is currently in Preview and will continue to be
improved on the road to GA.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I am doing some preliminary research on Windows Azure. The idea is to move 200+ ASP classic websites to Windows Azure. I am wondering if this is possible and feasible? Can I host that many websites on a single VM? Also note that each website needs to have its own set of email addresses.
There's absolutely no reason why you couldn't host all those sites on Azure VM (assuming you're talking about the preview Virtual Machine functionality). You get your own isolated machine, with its own IIS and IP. What you put on it is up to you, but it's no different than getting a VPS from any other company (rackspace etc.).
Obviously this is assuming that your sites are not very resource heavy and the memory etc. you get with different VM sizes can support the use.
Marek's answer isn't wrong, but please don't use "Virtual Machines" for this, and instead use Cloud Services (specifically, a web role). A web role lets you deploy just your code (in this case: websites) without having to mess with managing a full VM.
In short, PaaS is better than IaaS, as long as your app fits the model (which IIS-based websites do in Windows Azure).
I don't know what "each website needs to have its own set of email addresses" means or how it relates.