Problem przy tworzeniu Azure Active Directory B2C

Potrzebuję katalogu Azure B2C dla mojego projektu.

Przy próbie utworzenia nowego katalogu dostaję taki błąd:

The subscription is not registered to use namespace 'Microsoft.AzureActiveDirectory'.
See https://aka.ms/rps-not-found for how to register subscriptions.

 

Rozwiązanie:

 

1. Zaloguj się do Azure
2. Otwórz konsolę
    

3. Konsola może wymagać stworzenia katalogów.
4. W konsoli wpisz:

az provider register --namespace Microsoft.AzureActiveDirectory

 

Po kilku minutach powinno zadziałać. Możesz spróbować stworzyć katalog jeszcze raz.

 

Promo

Web.config changing when publishing application - how to avoid it?

I have MVC website, that I deployed to Azure. The application uses EF Code First. 

After deployment, these lines were added to web.config:

  <connectionStrings>
    <add name="LoremIpsum.LoremContext" 
         connectionString="LoremIpsum.LoremContext_ConnectionString" 
         providerName="System.Data.SqlClient" />
  </connectionStrings>

This caused this error:

Format of the initialization string does not conform to specification starting at index 0.

I solved this by going to my Publish Profile (the .pubxml file) and deleted following lines:

  <ItemGroup>
    <MSDeployParameterValue Include="$(DeployParameterPrefix)LoremIpsum.LoremContext-Web.config Connection String">
      <ParameterValue>... my actual connection string ...</ParameterValue>
    </MSDeployParameterValue>
  </ItemGroup>
  <ItemGroup>
    <_ConnectionStringsToInsert Include="LoremIpsum.LoremContext" />
  </ItemGroup>

Local Security Authority problem

Ever tried to log in to your remote computer, only to see this error message?

An authentication error has occurred. The Local Security Authority cannot be contacted.

I have my Azure Virtual Machine configured in domain. The Domain Controller and DNS is also an Azure VM. I'm trying to log in with my domain credentials. This error means, that the remote machine cannot access domain controller.

This error often occurs (or rather always and only) after I restarted VM - e.g. to change number of cores or memory.

Solution:

1. Log in to VM using local user, not domain one.

2. Open network and sharing center.

3. Click "Change adapter settings". As you can see, Windows cannot identify your domain.

4. Right-click network card icon, open Properties, double-click "Internet Protocol Version 4".

5. DNS server address disappeared. Set it again.

6. Now, you're back in domain. Log out and log in with domain credentials.

Creating SharePoint 2013 on Azure VMs - checklist

Follow this checklist to create SharePoint 2013 Server with configuration database on separate Virtual Machine.

1. Create Network in Azure
2. After that create two VMs - first with SQL, second with SP
3. During creating, add them both to the same Network
4. Log into first VM - the SQL one. Add AD DS feature and promote it to domain controller
5. Create domain user, that will be SP SQL user.
6. Open SQL Management Studio and create login and permissions for SP SQL user
7. Open Windows Firewall and set inbound rule for port 1433 (SQL Server)
8. Go to Azure and create endpoint for first VM for port 1433
9. Log into second VM - the SP one. Join it to domain.
10. Start SP Configuration Wizard, Create new server farm, use SP SQL user to create configuration DB, configure the rest