Azure SQL – is it possible to assign CREATE PROCEDURE permission for the master database?

I am trying to add a stored procedure to the master database (I deliberately am trying this for the master db) on Azure SQL. Is this possible? I suspect the answer is “no”, but I’d like to see some confirming documentation on it if that is the case.

What I’ve tried so far:

Here’s the procedure (just as a test):


I’ve tried the above using the admin login, and it failed:

Msg 262, Level 14, State 18, Procedure blah, Line 2 (Batch Start Line 21)
CREATE PROCEDURE permission denied in database 'master'.

I then tried to create another login and user and then assigned them to the “dbmanager” role and tried the create procedure again – same failure.

azure ad – Access Denied error After migrate on-prem Local AD SP Database to Sharepoint Farm joined to AzureAD DS

I have migrated Sharepoint 2013 Farm which is joined to Local AD DS to Sharepoint 2016 Farm joined to AzureAD DS.

Client wants to take full use of AzureAD DS and want to migrate sharepoint farm to Azure VMs connected to AzureAD DS.

I created a Sharepoint 2016 farm. created normal webapp/Site collection and is able to access as expected.

When I attach sharepoint 2013 DB after upgrade it gives access denied to those upgrade web app.
Do I need to do any changes to existing usernames as they has been now talking to AzureAD DS instead of Local AD.


Before the update on Microsoft Azure deployment Center i can connect my gitlab repository and the portal successfully fetched the commits. But after the update i cannot deploy my gitlab repository to the Azure portal the same way. Does anyone know how to fix this?

Image for reference. Thanks!


sql – Como utilizar EF Core Code First no Azure Synapse

Estou tentando utilizar migrações para gerenciar esquemas de banco de dados com o Entity Framework Core e C# no Azure Synapse, quando executo o comando update-database recebo uma mensagem de erro conforme descrito abaixo:

Enforced unique constraints are not supported. To create an unenforced unique constraint you must include the NOT ENFORCED syntax as part of your statement.

Esse erro ocorre pelo fato do Azure Synapse não aceitar o uso de PRIMARY KEY sem que a mesma esteja acompanhada por NONCLUSTERED e NOT ENFORCED. O script abaixo funciona perfeitamente quando executado no msqlms:

CREATE TABLE dbo.sample_table
    c1 int IDENTITY(1,1) NOT NULL,
    c2 char(10) NULL,
    c3 datetime NULL


Para incluir NONCLUSTERED pelo mapeamento do EF basta apenas definir IsClustered(false) conforme exemplo abiaxo.

public class ManifestationMap : IEntityTypeConfiguration<Manifestation>
    public void Configure(EntityTypeBuilder<Manifestation> builder)

        builder.HasKey(prop => prop.Id)
           .IsClustered(false); // Include NONCLUSTERED 

Não encontrei nenhuma solução para incluir pelo EF o NOT ENFORCED.

Obs: Não tenho esse problema quando estou utilizando o Azure SQL Server, nem quando utilizo Sql Server instalado localmente, apenas no Azure Synapse (Sql Server DW).

Azure Event Hub vs Event Grid or something else?

I have a timer function that calls a group of APIs asynchronously and then converts the XML responses to SQL Server records to an on premises database. I want to send a message in case there is a failure in the response so that I can retry the API call. After reading the documentation for Event Hubs and Event Grids, I’m not sure if either one of those options satisfies my requirement. The following is the documentation I’ve read:

Any insight would be appreciated.

c++ – LookupAccountNameW returning Failed (0x534) when user log on via Azure

I am running this code:

LookupAccountNameW(NULL, (LPCWSTR)UserName.c_str(), NULL, (LPDWORD)&UserSIDSize, NULL, (LPDWORD)&DomainNameSize, &SidType);

But noticed that when the user is an Azure user, it will returns:
1332 (0x534)

Again this issue is not seen if the user is local or part of an attached domain. Did I do something wrong, or am I missing something?