How can we improve the Azure Resource Manager?

← Azure Resource Manager

Add DateTime calculation Capabilities with utcnow() in ARM Templates

Having the possibility to generate SAS Tokens using listaccountsas() is a great step forward in arm template functions as it enables us to generate tokens to make use of linked templates residing on protected storage. However, we still have to provide a static value for token expiration to make use of that function.
Being able to use datetime calculation functions together with utcnow() would enable us to close a gap and generate SAS tokens dynamically.

A possible scenario could look like:

addhours(parameters(utcnow(),1))

and provide the result as expiration time inside the listaccountsas() function

39 votes
Sign in
(thinking…)
Sign in with: Microsoft
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Fabian Flanhardt shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
triaged  ·  Adminazurecxpuservoice (Product Manager, Microsoft Azure) responded  · 

Thanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.

5 comments

Sign in
(thinking…)
Sign in with: Microsoft
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Anonymous commented  ·   ·  Flag as inappropriate

    This is making it impossible to create an automation schedule as well, because the start time needs to be in the future (by at least 5 minutes)

    {
    "type": "Microsoft.Automation/automationAccounts/schedules",
    "apiVersion": "2015-10-31",
    "name": "[concat(parameters('automationAccountName'), '/Nightly Run 2')]",
    "dependsOn": [
    "[resourceId('Microsoft.Automation/automationAccounts', parameters('automationAccountName'))]"
    ],
    "properties": {
    "startTime": "2019-06-16T02:00:00-05:00",
    "expiryTime": "9999-12-31T17:59:00-06:00",
    "interval": 1,
    "frequency": "Day",
    "timeZone": "America/Chicago"
    }
    },

  • haavardg commented  ·   ·  Flag as inappropriate

    A workaround is splitting the date up, and use the add() function to add to either the hour or day:

    {
    "$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
    "contentVersion": "1.0.0.0",
    "parameters": {
    "utcDateDD": {
    "type": "string",
    "defaultValue": "[utcNow('dd')]"
    },
    "utcDateMM": {
    "type": "string",
    "defaultValue": "[utcNow('MM')]"
    },
    "utcDateYYYY": {
    "type": "string",
    "defaultValue": "[utcNow('yyyy')]"
    }
    },
    "variables": {
    "start-date": "[concat(parameters('utcDateYYYY'),'-', parameters('utcDateMM'),'-', add(int(parameters('utcDateDD')), 1))]"
    },
    "resources": [
    ],
    "outputs": {
    "starttime": {
    "type": "string",
    "value": "[concat(variables('start-date'),'T01:00:00+01:00')]"
    }
    }
    }

  • Klaas Demter commented  ·   ·  Flag as inappropriate

    Hi,
    this is coming from an issue with creation of Advanced Update Schedules (startTime needs to be in future)

    I would suggest to actually implement date as it is done in unix. Then you could simply say something like date(now + 1 hour) or date(tomorrow 13:00) etc

  • Fabian Flanhardt commented  ·   ·  Flag as inappropriate

    Looks like it was a little late when I posted the example. Here is a more accurate one: ;-)

    addhours(parameters('utcnow'),1))

Azure Resource Manager

Categories

Feedback and Knowledge Base

(thinking…)
Hosted by UserVoice