I have a trial snowflake account with url like ie1234.azure.snowflakecomputing.com
I'd like to convert it to paid one for my company and wondering if is possible to change account name to be my company name rather than ie1234?
If I read documentation correctly, account name is generated by snowflake and I cannot configure it unless I'm missing something. Seems strange...
Thanks
Once you have a paid account rather than a trial account, you can contact your Sales Engineer and request an alias. The URL will still end with the Azure deployment and then snowflakecomputing.com, but you can request a subdomain for your company name if it's still available. The "license plate" name and "vanity plate" name will both work then.
Snowflake just released the ability for the Orgadmin Role to rename accounts without Support:
ALTER ACCOUNT <account_name> RENAME TO <new_account_name> [ SAVE_OLD_URL = { TRUE | FALSE } ]
https://docs.snowflake.com/en/sql-reference/sql/alter-account.html#syntax
Related
According to this article (https://docs.snowflake.com/en/user-guide/admin-account-identifier.html#), SnowFlake has two different ways for account IDs:
Account name - created by me, for example, my-company.snowflakecomputing.com
Account locator - a more technical name, not as nice and understandable as 1)
Now we are using locator and I don't understand, it is possible to change locator to name or not?
P.S. I read, that account locator can't be changed, but maybe this is only true for changing locator to locator?
It is possible to change the account alias and access your account via a new name, if you are using the Organizations-Feature. Now I assume your account is not part of an organization, so we have to use the "Option 2" of the below link (same as yours).
So... no, it is not possible to change, if you created your account on your own through self-service. Only if a Snowflake representative is creating your account, then this person can change to a name.
Docs: https://docs.snowflake.com/en/user-guide/admin-account-identifier.html
The account locator can not be renamed/modified once the account is created.
https://docs.snowflake.com/en/user-guide/admin-account-identifier.html#option-2-account-locator-in-a-region
Your account name is the alias for your account locator, and it can be renamed (by support). If you want to connect to your Snowflake account, using the account name, you need to use the orgname-accountname.snowflakecomputing.com format.
Btw, all accounts also have a "random" organization name. Support will tell your organization name or rename it if you request.
Changing Account Name:
An organization administrator (i.e. a user granted the ORGADMIN role) can use the ALTER ACCOUNT command to rename an account. For example, the following command renames an account called original_acctname to new_acctname:
use role orgadmin;
alter account original_acctname rename to new_acctname;
By default, Snowflake allows you to access the renamed account with either the original URL or the URL that contains the new account name. To prevent access using the old URL, set the optional SAVE_OLD_URL parameter to FALSE when renaming the account. If the account has already been renamed without this parameter, you can still block the old URL by executing the ALTER ACCOUNT new_acctname DROP OLD URL command.
I'm setting up SAML SSO for an application. I have it working except that I'm unable to return a suitable value for the NameID claim. Existing userid's in the application are firstname + last initial so they don't match display names, email addresses, or any of the typical stuff found in Azure AD. I could use a transform to generate that but the available functions don't appear to do what I need.
I could also manually enter the userid in Azure AD and then map the claim to that but I hate to "misuse" an existing field (e.g. putting the userid in user.jobtitle or some such).
I also don't want to have to change everyone's userid in the app to match something that already exists in Azure.
I feel like I'm missing something obvious here since there have to be a lot of apps that don't use a common Azure property as their userid.
Thanks in advance for any help here!
Tom
You can map the attributes & claims present in the active directory to your app fields. For example if user.givenname is present in the active directory and in your app, the field name is firstName, you can achieve this by doing the mapping in manage claim section of User attributes & claims. Same could be done for others fields.
You go into the Enterprise applications > Your App > SAML-based Sign-on > click on edit
I'm new to managing a small company using Intune and Azure Active Directory. I need to create an email alias (info#, webmaster#, etc) and have those emails go to a specific user. I created a group with the email alias I want to use but this appears to be more of a shared email box that has to be logged into.
Can someone help me or point me to the correct MS docs to accomplish this?
I've tried googling for the answer to this question but maybe I'm not using the correct search terms.
You could add email alias in Microsoft 365 admin center.
Please refer to the detailed steps: Add email aliases to a user。
Note the step 2:
On the Active Users page, select the user > Manage email aliases.
You won't see this option if the person doesn't have a license assigned to them.
So you need to make sure the user has Exchange Online license.
I have an Azure Active Directory (AAD) set up in my Azure subscription associated with an email address of mine, which we'll call A.
Some time later, I updated my Microsoft Account to use a new email address B as the primary email address, with A being associated with it still so it can still be used and the two email addresses treated as being one.
In AAD there is one user, whose user Id is A which appears not to be able to be changed as it is greyed-out. Attempting to add B fails with the error: You cannot add yourself.
Is there a way I can force the user name of the AAD user to be B instead of A?
The reason I ask is because I am trying to setup an Azure Key Vault in my subscription as it appears to be failing because whether or not I sign in as A or B in Azure Powershell, I am always signed in as B. This then causes this error message, which I appear to be unable to work around:
New-AzureKeyVault : Cannot find the Active Directory object 'B' in tenant
'{Tenant Id}'. Please make sure that the user or application service principal you are
authorizing is registered in the current subscription's Azure Active directory. The TenantID displayed by the cmdlet
'get-AzureSubscription -current' is the current subscription's Azure Active directory.
Can you check that you are using the latest bits for Key Vault PowerShell?
I talked with some folks internally and we believe that an experience like this may be expected if you are using an older version of the PowerShell CMDLETs, but the lastest version should be update to date and not run into the issue you are having.
If you find that you still hit this issue after upgrading, we may have a bug on our side that we should fix.
In that case, my suggestion is for you to create a new Admin User. Then delete the old Admin Account (you may need to Transfer Onwership of your AAD Subscription to the new Admin), and then recreate your account, which will pull the lastest information from that user.
However, I only reccommend trying this after having updated the PowerShell bits.
Please let us know if either of these methods resolves your issues.
Thanks,
Shawn Tabrizi
We're using Active Directory to manage some of the accounts in our Sitecore instance. In the database the usernames are in the domain\username format (as you'd expect).
In Sitecore, I can do
var user = User.FromName(item["__Created by"], true)
and I get back a user object, but I can't seem to get the Guid associated with the user in the aspnet_Users table.
Other than using AD, we're not doing anything funny with the membership provider.
Edit: I probably should have stated: I've got the ProviderUserKey but it's not the UserId from the aspnet_Users table as it would be if this were using the membership provider that comes with Sitecore, it's very different (it's of type System.Security.Principal.IdentityReference.SecurityIdentifier if anyone is interested)
This is not possible without directly querying the database. You could write an extension method that queries the database for the User, but I would recommend not using a database field that is intentionally hidden/abstracted by the API. If you provide more info on why you wanted to get the UserId, we might be able to help you find some alternatives.