Hotmail Sign In

[Pavan Outlaw]

Whilesigning in, select Yes at the "Stay signed in?" prompt if you want to go straight to your mailbox next time (not recommended for shared computers). Alternatively, check the "Don't show this again" box and select No to be prompted for your password each time.

Microsoft always keeps an eye out for unusual sign-in activity, just in case someone else is trying to get into your account. If you're travelling to a new place or using a new device, we might ask you to confirm that it really is you.

I have 1 Hotmail account and 2 Gmail accounts. For a long time now I have used my Hotmail address within the Gmail app to send and receive emails to and from Hotmail address. Now I have been told via email to said address that I can no longer use my Hotmail address to "send" emails only to "receive" emails. I have spent on and off the last 3 weeks on Google to try and find answers. I have been on Google's forum but I have not had any answers. And to be perfectly honest I want to close my hotmail.account. I sign into Microsoft to delete account and it requires verification. Trouble is my phone number that was initially set up I no longer have and cannot change it without that verification code. I have Microsoft Authenticator app and cannot use the codes that have been generated by them. I have registered my Gmail account with Microsoft with new phone number but am at a loss as to what I should do.

First off I installed Microsoft Authenticator app. Signed in, but it required verification of my identity. Options were... "Approve request on Authenticator app or use a verification code from mobile app". Or " I have a code" or " Show more verification methods" If I chose that method it the shows ******* and the last 2 digits of my mobile number. Unfortunately the mobile number is my old mobile number and I cannot update to my new mobile number until I can verify my identity ? Then there is a option " Don't have any of these"chose that option and it gives a link to update my security information. Went to that link, signed in and took to "Verify your identity"

All I want to do is update my mobile number and then tbh I want to remove my Hotmail account as I'm totally fed up trying to fix this. I have set up my Gmail account on Microsoft and have all the correct details. If there is a way for me to change my mobile number on my Hotmail account, if I then remove said Hotmail account will all my information still be available when I sign into Microsoft via my Gmail account?

Did you know you can try the features in Microsoft Defender XDR for Office 365 Plan 2 for free? Use the 90-day Defender for Office 365 trial at the Microsoft Defender portal trials hub. Learn about who can sign up and trial terms here.

DomainKeys Identified Mail (DKIM) is a method of email authentication that helps validate mail sent from your Microsoft 365 organization to prevent spoofed senders that are used in business email compromise (BEC), ransomware, and other phishing attacks.

If you use only the Microsoft Online Email Routing Address (MOERA) domain for email (for example, contoso.onmicrosoft.com): You don't need to do anything. Microsoft automatically creates a 2048-bit public-private key pair from your initial *.onmicrosoft.com domain. Outbound messages are automatically DKIM signed using the private key. The public key is published in a DNS record so destination email systems can verify the DKIM signature of messages.

But, you can also manually configure DKIM signing using the *.onmicrosoft.com domain. For instructions, see the Use the Defender portal to customize DKIM signing of outbound messages using the *.onmicrosoft.com domain section later in this article.

If you use one or more custom domains for email (for example, contoso.com): Even though all outbound mail from Microsoft 365 is automatically signed by the MOERA domain, you still have more work to do for maximum email protection:

Configure DKIM signing using custom domains or subdomains: A message needs to be DKIM signed by the domain in the From address. We also recommend configuring DMARC, and DKIM passes DMARC validation only if the domain that DKIM signed the message and the domain in the From address align.

For email services that aren't under your direct control (for example, bulk email services), we recommend using a subdomain (for example, marketing.contoso.com) instead of your main email domain (for example, contoso.com). You don't want issues with mail sent from those email services to affect the reputation of mail sent by employees in your main email domain. For more information about adding subdomains, see Can I add custom subdomains or multiple domains to Microsoft 365?.

Email authentication protection for undefined subdomains is covered by DMARC. Any subdomains (defined or not) inherit the DMARC settings of the parent domain (which can be overridden per subdomain). For more information, see Set up DMARC to validate the From address domain for senders in Microsoft 365.

If you own registered but unused domains: If you own registered domains that aren't used for email or anything at all (also known as parked domains), don't publish DKIM records for those domains. The lack of a DKIM record (hence, the lack of a public key in DNS to validate the message signature) prevents DKIM validation of forged domains.

DKIM alone is not enough. For the best level of email protection for your custom domains, you also need to configure SPF and DMARC as part of your overall email authentication strategy. For more information, see the Next Steps section at the end of this article.

We provide instructions to create CNAME records for different Microsoft 365 services at many domain registrars. You can use these instructions as a starting point to create the create the DKIM CNAME records. For more information, see Add DNS records to connect your domain.

You use the Defender portal or Exchange Online PowerShell to view the required CNAME values for DKIM signing of outbound messages using a custom domain. The values presented here are for illustration only. To get the values that are required for your custom domains or subdomains, use the procedures later in this article.

In Microsoft 365, two public-private key pairs are generated when DKIM signing using a custom domain or subdomain is enabled. The private keys that are used to sign the message are inaccessible. The CNAME records point to the corresponding public keys that are used to verify the DKIM signature. These records are known as selectors.

To use the procedures in this section, the custom domain or subdomain must appear on the DKIM tab of the Email authentication settings page at =DKIM. The properties of the domain in the details flyout must contain the following values:

We provide instructions to create CNAME records for different Microsoft 365 services at many domain registrars. You can use these instructions as a starting point to create the DKIM CNAME records. For more information, see Add DNS records to connect your domain.

As described earlier in this article, the initial *.onmicrosoft.com domain is automatically configured to sign all outbound mail from your Microsoft 365 organization, and you should configure custom domains to DKIM signing of outbound messages.

To use the procedures in this section, the *.onmicrosoft.com domain must appear on the DKIM tab of the Email authentication settings page at =DKIM. The properties of the *.onmicrosoft.com domain in the details flyout must contain the following values:

If you'd rather use PowerShell to enable DKIM signing of outbound messages using a custom domain, or to customize DKIM signing for the *.onmicrosoft.com domain, connect to Exchange Online PowerShell to run the following commands.

Before you can configure DKIM signing using the custom domain, you need to add the domain to Microsoft 365. For instructions, see Add a domain. To confirm that the custom domain is available for DKIM configuration, run the following command: Get-AcceptedDomain.

As described earlier in this article, your *.onmicrosoft.com domain is already signing outbound email by default. Typically, unless you've manually configured DKIM signing for the *.onmicrosoft.com domain in the Defender portal or in PowerShell, the *.onmicrosoft.com doesn't appear in the output of Get-DkimSigningConfig.

For a custom domain, if Microsoft 365 is able to detect the CNAME records at the domain registrar, the command runs without error, and the domain is now used to DKIM sign outbound messages from the domain.

If the CNAME records aren't detected, you get an error that contains the values to use in the CNAME records. Check for typos in the values at the domain registrar (easy to do with the dashes, periods, and underlines!), wait a while longer, and then run the command again.

For the same reasons that you should periodically change passwords, you should periodically change the DKIM key that's used for DKIM signing. Replacing the DKIM key for a domain is known as DKIM key rotation.

When you do a DKIM key rotation on a domain as described in this section, the change isn't immediate. It takes four days (96 hours) for the new private key to start signing messages (the RotateOnDate date/time and the corresponding SelectorAfterRotateOnDate value). Until then, the existing private key is used (the corresponding SelectorBeforeRotateOnDate value).

3a8082e126