This is mailjet's instruction to set up SPF.
And this is my setup in Google Domains. Can't figure out what I'm missing
The issue was that the SPF records conflicted with Google Workspace records which are not editable. The workaround was to fully delete the Google Workspace record from the Synthetic records section and re-create them manually in the Custom resource records and include mailjet.
Related
I explicitly created an Availability Set via the Azure console. I can launch VM's in successfully by selecting the Availability Set.
When I review the Availability Set in the console, I do not have an option to edit the Fault Domain or Update Domains values.
Are there options to perform this Action?
Yes, you can use REST api, or resources.azure.com to edit those values. Powershell\Cli have commands to edit those (Update-AzAvailabilitySet).
It appears these values are read only after creating the resource
We have a CSP subscription through a partner, and the whole experience is rubbish. Costing / billing APIs not available, can't use our Office 365 Azure AD, can't use SendGrid, can't see the cost of resources in the portal, loads of features missing. It's rubbish.
We're moving away and want to transfer a substantial number of SQL Azure servers (with many pools and databases) and Storage Accounts (with lots of items) to another, new PAYG subscription, which uses our O365 Azure AD.
#AzureSupport on Twitter pointed me to - https://learn.microsoft.com/en-us/azure/azure-resource-manager/resource-group-move-resources
But this says, "The source and destination subscriptions must exist within the same Azure Active Directory tenant."
It suggests two ways forward:
https://learn.microsoft.com/en-us/azure/active-directory/fundamentals/active-directory-how-subscriptions-associated-directory
But... The "Change Directory" option is not present for CSP accounts (lo and behold! another missing feature)
https://learn.microsoft.com/en-us/azure/billing/billing-subscription-transfer
But.. Heading to https://account.windowsazure.com/Subscriptions as instructed gives me a 500 error, with "We are sorry, but we could not complete that operation.".
Also.. Of course, the CSP (Ingram) do not offer any of these kinds of options on their sub management portal.
#AzureSupport then recommended I post here.
Can anyone advise / help please? Would be very much appreciated, thank you.
You are currently blocked, as there is not a good workflow to migrate from CSP to Pay-as-you-go, as the below User Voice entry suggests others are looking for the same. Please up vote and comment on this.
Change subscription from CSP to pay-as-you-go
As for getting switched back to PAYG, I suggest exporting your data and importing in to new services that have been set-up under your desired account set-up. If you need the instance names, these will need to be deleted before the data can be imported into the newly created service with the existing instance names, in cases where instances names can be reused after deletion of the particular service.
There is currently no supported means to migrate a subscription away from CSP once migrated, from my investigation.
Use Azure Data Migration Service to migrate from source to target. This though, will not allow you to keep the same instance names, as both the source and target will need to exist at the same time.
When I try to create a backend pool in the azure portal, I don't get prompted for an availability set; I just see a drop-down list of virtual networks but the list is empty.
When I first tried this I didn't know about availability sets. I have now created an availability set but I still don't get any option to select an availability set either when creating a backend pool or when creating a new VM.
I have seen tutorials and videos on setting up load balancing on azure, but on my azure portal I just don't see the same options they have in the screenshots.
Are availability sets still relevant or are they now deprecated? if they are still in use, is there anything I need to do to enable them?
Availability Sets are not deprecated.
If you create an Availability Set in the same Resource Group with the Load Balancer you must be able to see it.
And one more thing, when you must select the Availability Set while you create a Virtual Machine you cannot add it if the virtual machine already exists.
Hmm, after looking more closely I realized that in the 3rd step for creating the VM, the screen wasn't loading completely. As well as the Availability Set selection being completely blank, a couple of the other drop-down boxes just said "loading..." next to them so basically I couldn't create a VM at all.
I tried waiting for a while, logging out and back in etc but it made no difference. I tried on a different Azure subscription and everything worked as expected. The original subscription used to work, so I suspect my Availability set had somehow not been created properly and this was causing the screen to bork.
I deleted the Availability set and created another one with all the same parameters, and now it seems to be working properly.
I want to create a azure document DB under staging subscription, in future i'll be moving that DB to production subscription but i need to create that document DB with custom domain name .
say for example, by default the document DB URI will be xxx.documents.azure.com:443, but i need the it is xxxx.mydomain.com:443, Is that possible, if so how to do that?
You could set up your own proxy to accomplish this. Other than that, I do not know of a way to do that but in general this is not needed because DocumentDB is designed to be hit by your application server not the end user. Under these circumstances, it poses no issue for the url to be ...azure.com.
If we understood why you wanted this, we might be able to help you accomplish that goal some other way.
I am completely new to Microsoft Azure. I know very little about it. I have a MVC 5 app which I created that I'd like to possibly host on Azure. Do I purchase a domain name first and then move it over to Azure? If not, how does this work?
You can do it either way. If you create web site in Azure you get mysite.azurewebsites.net url for it, which you can then change to your domain when you purchase it.
Or you can purchase the domain name first and straight away change NS records to point over there once you move your site to Azure.
It's really flexible and there is no restrictions to it.
The process in more detail goes roughly like this:
When you try to set the domain name for your site, Azure gives you certain records you need to set in NS tables.
Where you have bought the domain name, make sure you have access to alter the NS records or contact support to do it for you.
Insert the 2 records Azure tells you to.
After the change has propagated, you will see green light in Azure as it accepts the new domain name.
Done!