"Connect" to Azure resources


based upon current understanding, 1 of core design ideas behind web services (eg. azure service management rest api) apis stateless. prevented need "connect" services before leveraging capabilities, because each call authenticated, , provided of necessary information, ensure web service call succeed.

with azure automation, seems concept being tossed aside, since "core" sample runbooks connect-azure or connect-azurevm. seems me sample runbooks should simple, useful operations start-azurevm or stop-azurevm, instead of "connect" commands, don't provide useful value in , of themselves.

can please provide direction on azure automation feature headed, , why it's necessary "connect" azure resources, before leveraging capabilities? when using azure powershell module directly, outside of workflow, sma, or azure automation, it's not necessary "connect" resources. can run start-azurevm, stop-azurevm, or large array of other commands, without "connecting" them, or azure subscription itself. doesn't make sense me, logically speaking, "connect" azure subscription, since stateless api, why concept being proliferated azure automation?

cheers,
trevor sullivan
microsoft mvp: powershell

if post helpful, please click little "vote helpful" button :)

trevor sullivan
trevor sullivan's tech room
twitter profile

hi trevor,

these utility runbooks, not sample runbooks. meant called other runbooks make tasks easier. utility runbooks on script center , tagged "utility," while samples tagged "tutorial". have runbooks on script center doing things against azure, example one calls both start-azurevm , stop-azurevm. don't have runbooks starting or stopping vm because single cmdlet work, not make sense write full runbook that.

the reason connect-azurevm needed because gives uri use connect azure vm on winrm. adds vm's certificate locally worker running runbook remoting vm allowed.

connect-azure needed because azure cmdlets not stateless. require calling either set-azuresubscription, import-publishsettingfile, or add-azureaccount set connection azure. while need once when using azure cmdlets in ise, have every runbook execution in azure automation because runbooks run across many workers, , in sandboxes cleaned after execution, file azure cmdlets use know how talk azure, written filesystem using set-azuresubscription, import-publishsettingfile, or add-azureaccount, can not assumed still there between runbook executions. connect-azure calls set-azuresubscription internally, passing in certificate asset contains azure management certificate. however, azure supports non-interactive orgid cred auth via add-azureaccount, connect-azure going deprecated add newest azure module azure automation. expect blog post on using azure automation talk azure using orgid credential based auth soon.



Microsoft Azure  >  Azure Automation



Comments

Post a Comment

Popular posts from this blog

Azure DocumentDB Owner resource does not exist

having same error microsoft.azure.documents.documentclientexception: message: {"errors":["owner resource not exist"]} , scenario. when deployed webapp azure , try document docdb throws error. docdb exists in azure , contains document looking for. weird local machine(running vs) works fine. i'm using same settings in azure , local. have , idea this. thanks Microsoft Azure  >  Azure Cosmos DB
Read more

job syspolicy_purge_history job fail in sqlserver 2008

Image
hello guys, when installed sqlserver,it automatically created 1 job name job syspolicy_purge_history. but failed @ step 1. the reason is: date                11/6/2010 2:00:00 am log                job history (syspolicy_purge_history) step id                1 server                mxosv-otsdb01 job name                syspolicy_purge_history step name                verify automation enabled. duration                00:00:00 sql severity                16 sql message id                34022 operator emailed                operator net sent                operator paged                retries attempted                0 message executed user: nt authority\system. policy automation turned off. [sqlstate 42000] (error 34022).  the step failed. have run statement: select msdb.dbo.fn_syspolicy_is_automation_enabled the returned valus 0. what can resolve it? or can delete job manually.   thanks in advance. if haven't things want,be
Read more

Trying to register with public marketplace error with 'Get-AzureStackStampInformation'

when trying register against public azure adfs azure stack error below. logs can found at: c:\maslogs\azurestack.azureregistration.2017-10-12.01-31-23.log  and  \\azs-ercs01\c$\maslogs error occurred checking stamp information: system.management.automation.remoteexception: term 'get-azurestackstampinformation' not recognized name of cmdlet, function, script file, or operable program. check spelling of name, or if path included, verify path correct , try again. @ c:\azurestack-tools-master\registration\registerwithazure.psm1:1106 char:5 +     throw "logs can found at: $global:azureregistrationlog  and  \ ... +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + categoryinfo          : operationstopped: (logs can fou... , try again.:string) [], runtimeexception     + fullyqualifiederrorid : logs can found at: c:\maslogs\azurestack.azureregistration.2017-10-12.01-31-23.log  a    nd  \\azs-ercs01\c$\maslogs error occurred chec
Read more