Azure for SharePoint Developers - Workshop - Part 3: Web Services

Editor's Notes

• #2: WRK403 - What Every SharePoint Developer should know about Microsoft Azure While the SharePoint Framework is the new place to customize the SharePoint UI, it runs completely within the web browser, and does nothing to help with background processing or other server-side work, including situations where you need to elevate permissions beyond what the end user is allowed to do. Both sandboxed and farm solutions are off the table in SharePoint Online, leaving few SharePoint-based options for this kind of work. Fortunately, Microsoft Azure is well positioned to handle these situations and many more, and should be part of every SharePoint developer's tool set.This workshop will introduce Azure platform services including Azure Active Directory, web apps, logic apps, Azure Functions, and more. You will learn practical approaches to integrate these with SharePoint. Scenarios will include:• Surfacing line of business data in SharePoint via Azure web apps and functions• Elevating permission in a SharePoint web part• Using Azure functions as timer jobs and web services• Implementing workflows and business orchestration with Azure Logic Apps• Storing and querying large data sets (beyond 5,000 rows) in SQL Azure• Safely managing security and secrets in your Azure code with Managed Service Identities and Key VaultAttendees should have a working knowledge of C# development and familiarity with SharePoint Online.Don't miss this opportunity to upgrade your development skills for modern SharePoint!
• #3: 2
• #9: 4 STEP video demo 1. Create new project, get 401, comment out Authorize2. Open Azure AD fix up entry copy values 3. Test in Postman – 401 – fix headers, select right token – works! 4. Deploy to Azure works there too
• #10: 4 STEP video demo 1. Create new project, get 401, comment out Authorize2. Open Azure AD fix up entry copy values 3. Test in Postman – 401 – fix headers, select right token – works! 4. Deploy to Azure works there too
• #11: 4 STEP video demo 1. Create new project, get 401, comment out Authorize2. Open Azure AD fix up entry copy values 3. Test in Postman – 401 – fix headers, select right token – works! 4. Deploy to Azure works there too
• #12: 4 STEP video demo 1. Create new project, get 401, comment out Authorize2. Open Azure AD fix up entry copy values 3. Test in Postman – 401 – fix headers, select right token – works! 4. Deploy to Azure works there too
• #13: 4 STEP video demo 1. Create new project, get 401, comment out Authorize2. Open Azure AD fix up entry copy values 3. Test in Postman – 401 – fix headers, select right token – works! 4. Deploy to Azure works there too
• #22: Blue pill – go on believing what you want Red pill – all the way down the rabbit hole
• #35: A JSON template file is a text file that contains descriptions of the resources, configurations code and extensions. JSON templates are idempotent, which means that they can be run multiple times without changing the outcome beyond initial deployment. A consequence of this characteristic is that templates can be used to upgrade applications, for example, by scaling out applications with additional VMs. You modify the template to include the specifications for the additional virtual machines. When you deploy the template, Azure Resource Manager will recognize the resources that have previously been deployed and create only the resources that have been added. A JSON template is divided into sections: <CLICK> The $schema (a required element that provides the location of the file that describes the version of the template language) along with a required element that provides the version of the template The schema reference is used by intelligent JSON clients to determine the schema that is applicable to the JSON file and to provide additional functionality such as autocomplete and intellisense. <CLICK> Parameters (optional elements that define values that are passed in when the template is executed) The value for the Parameters key is an array of parameter objects that representing the dynamic input for the JSON template. Each of the parameter objects has a name that is used pass values in at runtime and is referenced within the JSON itself in other sections. For example, "NewStorageAccount" is the name of the parameter that is supplied as an input and used to provide the name of the storage account resource specified in the JSON file. <CLICK> Variables (optional elements that define the values that are used when template is executed) <CLICK> Resources (a required element that defines the resources that are deployed or updated in a resource group); and This slide doesn’t show it, but you can also have an optional Outputs section that defines values that are returned after a deployment <CLICK> A JSON file is constructed of key/value pairs. For example, in the image above, "ContentVersion" is the key and "1.0.0.0" is the value. A key is always a string enclosed in quotation marks. A value can be a string, securestring, number, boolean expression, array, or object. A JSON object is enclosed in curly braces, "{ }". In a key/value pair the key is always followed by a colon. Key/pairs are separated by commas. A JSON template may also contain functions and expressions. Expression are enclosed in square brackets, "[ ]', and can appear anywhere in a JSON string. Functions calls have the format functionName(arg1,arg2,arg3). Properties are referenced using the dot and index operators. The lab provides notes with additional details regarding specific parameters, variables, resources, etc. Authoring Azure Resource Manager templates https://azure.microsoft.com/en-us/documentation/articles/resource-group-authoring-templates/
• #66: In general don’t worry about it As you scale out, fabric controller will put instances into different fault domains
• #68: https://docs.microsoft.com/en-us/azure/sql-database/sql-database-designing-cloud-solutions-for-disaster-recovery