Windows live id register application

Add security info. Your security info helps protect your account. We'll use this to help you recover your password, help keep hackers out of your account, and get in if you get blocked. We won't use it for spam. Add phone number Add email. We can't complete this upgrade right now. Try again soon. Sorry about that. You can still play Minecraft as usual. You're going to need a parent for this. You'll configure a redirect URI in the next section. When registration finishes, the Azure portal displays the app registration's Overview pane.

You see the Application client ID. Also called the client ID , this value uniquely identifies your application in the Microsoft identity platform. New app registrations are hidden to users by default. When you are ready for users to see the app on their My Apps page you can enable it.

Then on the Properties page toggle Visible to users? Your application's code, or more typically an authentication library used in your application, also uses the client ID. The ID is used as part of validating the security tokens it receives from the identity platform.

A redirect URI is the location where the Microsoft identity platform redirects a user's client and sends security tokens after authentication. You add and modify redirect URIs for your registered applications by configuring their platform settings. Settings for each application type, including redirect URIs, are configured in Platform configurations in the Azure portal.

Some platforms, like Web and Single-page applications , require you to manually specify a redirect URI. For other platforms, like mobile and desktop, you can select from redirect URIs generated for you when you configure their other settings. Under Configure platforms , select the tile for your application type platform to configure its settings. There are some restrictions on the format of the redirect URIs you add to an app registration. Credentials are used by confidential client applications that access a web API.

Examples of confidential clients are web apps, other web APIs, or service-type and daemon-type applications. Credentials allow your application to authenticate as itself, requiring no interaction from a user at runtime.

You can add both certificates and client secrets a string as credentials to your confidential client app registration. Sometimes called a public key , a certificate is the recommended credential type because they're considered more secure than client secrets.

For more information about using a certificate as an authentication method in your application, see Microsoft identity platform application authentication certificate credentials. Sometimes called an application password , a client secret is a string value your app can use in place of a certificate to identity itself.

Client secrets are considered less secure than certificate credentials. Application developers sometimes use client secrets during local app development because of their ease of use. However, you should use certificate credentials for any application you have running in production. This can contain multiple registry values to indicate which schemes are supported. This string follows the format of scheme1:scheme2. If this list is not empty, file: will be added to the string.

This protocol is implicitly supported when SupportedProtocols is defined. Indicates that your application can accept a URL instead of a file name on the command line. Applications that can open documents directly from the internet, like web browsers and media players, should set this entry. For example, if the application has this entry set and a user right-clicks on a file stored on a web server, the Open verb will be made available.

If not, the user will have to download the file and open the local copy. In Windows Vista and earlier, this entry indicated that the URL should be passed to the application along with a local file name, when called via ShellExecuteEx.

In Windows 7, it indicates that the application can understand any http or https url that is passed to it, without having to supply the cache file name as well. This registry key is associated with the SupportedProtocols key. Provides the verb method for calling the application from OpenWith. Without a verb definition specified here, the system assumes that the application supports CreateProcess , and passes the file name on the command line.

Enables an application to provide a specific icon to represent the application instead of the first icon stored in the. Provides a way to get a localizable name to display for an application instead of just the version information appearing, which may not be localizable.

If that name is missing, the association query defaults to the display name of the file. Lists the file types that the application supports. Doing so enables the application to be listed in the cascade menu of the Open with dialog box. Indicates that no application is specified for opening this file type.

Be aware that if an OpenWithProgIDs subkey has been set for an application by file type, and the ProgID subkey itself does not also have a NoOpenWith entry, that application will appear in the list of recommended or available applications even if it has specified the NoOpenWith entry.

Indicates that the process is a host process, such as Rundll Such shortcuts are candidates for inclusion in the MFU list. Indicates that the application executable and shortcuts should be excluded from the Start menu and from pinning or inclusion in the MFU list. This entry is typically used to exclude system tools, installers and uninstallers, and readme files.