S4S in Azure PaaS

Once you have your Sitecore instance running in Azure, you can proceed to install the core S4S Sitecore package the same as if you were installing in a local or VM instance.

There are a few differences when working with the Azure dashboard and infrastructure.

Logging: Where is it?

Open

This screenshot is using Cloud Explorer in Visual Studio to get to the Azure resources

The azure.log.xxxx has all the relevant logging related to S4S function and troubleshooting

Here’s a tasty one:

Open

This message is indicating that the model xml files have not been copied into the XConnect site!

Further troubleshooting

• Is Azure configured to use Application Insights instead of logging to file? See Sitecore documentation or this blog post for additional information.

• The Kudu tool can be used to search for the latest logs on file, and access files currently locked. More information.

Next Step

SF Callouts in Azure PaaS

Steps